PsychoDazey
asked on
ORA-12514 and Net configuration assistant
I am using Oracle 10g on Windows server 2003. I installed the 10g client on a different pc on the network and used the Net Configuration Assistant/Local Net Service Name Configuration tool to configuration the netservice names. Each time I configured a name it would blow up because it is trying to use the system account and the password is wrong. If I change the login to sysman with the correct password it succeeds. I then try to schedule a job to run and get a ORA-12514 error. if I check the net configuration assistant the login is changed back to system.
Another weird piece of the puzzle is if I try to log on to a database through Enterprise Manager from the remote server as sysdba it says Insufficient privileges. If I log on as normal it works. If I go to database server and log on with the same credentials I can connect as sysdba....PLEASE HELP! I cannot for the life of me figure out what is going on. Its like the remote server is trying to resolve my credentials locally.
Another weird piece of the puzzle is if I try to log on to a database through Enterprise Manager from the remote server as sysdba it says Insufficient privileges. If I log on as normal it works. If I go to database server and log on with the same credentials I can connect as sysdba....PLEASE HELP! I cannot for the life of me figure out what is going on. Its like the remote server is trying to resolve my credentials locally.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
'SERVICE_NAME' parameter - if so, verifiy that it corresponds exactly to the
target database's SERVICE_NAMES INIT.ORA parameter value including DB_DOMAIN,
if configured. To check the value, run:
SQL> show parameter service_names
If you continue to receive ORA-12514, ensure the Database has successfully
registered with the Listener. To check the value, run:
LSNRCTL> status <listener-name>
If you continue to receive ORA-12514, you may attempt to workaround the error
by modifying the client TNSNAMES.ORA service name to use '(SID=...)', rather
than '(SERVICE_NAME=...)'. Doing so reverts back to traditional referencing of
hard-coded Database SIDs from the SID_LIST_LISTENER section of the LISTENER.ORA.
This should avoid the error.
Following is an example TNSNAMES.ORA that would result in error:
V817 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = myserv)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = V817) #Change SERVICE_NAME to SID OR
# (SERVICE_NAME = V817.DOMAIN) #Correct SERVICE_NAME - include DB_DOMAIN
)
)