ORA-12546 When connecting without specifying sid in connect string

I am currently having a difficult time connecting to an Oracle 9.2.0.4 database running on Red Hat Linux.
I can successfully connect to this database with sqlplus as oracle whether a sid name is included in the connect string or not. I can also successfully connect to the instance through jdbc with jsp pages. However when I try to connect as root without specifying the sid I get an ORA-12546 TNS: Permission denied. I also receive this error when attempting to connect to the instance through php scripts. Note that root can connect through sqlplus with no problem as long as the sid is included in the connect string. Also note that the oracle user can connect either way.
I turned on tracing and found that this error is occurring before it even gets to the listener as no log or trace entries are generated when the error occurs.
Does anyone have any ideas?

did you set the parameter TWO_TASK ?

Similar Messages

Getting ORA-1013 when attempting to expand tables within connections

Getting ORA-1013 when attempting to expand tables within connections on new install of Oracle SQL developer 3.1.06.
Any ideas?

Hi Steve,
The ORA-01013 usually means a timeout or, more typically on this forum, an intentional user cancellation. Searching the forum, I do not see any prior references to your exact situation. Some recommendations:
1. SQL Developer 3.1.0.6 was an early adopter release. Upgrade to the latest and greatest: 3.2.10.09.57
2. Review this: Re: [SQL Developer 3.0.04] Cannot Drill Down
3. If it is a true timeout, your privileges might make a difference. If you have access to the DBA views, SQL Developer does look-ups using those and performance is better.
So for [3], having the SELECT_CATALOG_ROLE privilege may help. I even read of one case in this forum where the poster finally discovered his database's recycle bin had an issue and the DBA needed to do some clean-up to correct the performance issue.
Hope this helps,
Gary
SQL Developer Team

Unable to connect without specifying port number

I have a strange situation on the client side. While connecting to sqlserver remotely, and when the instance is set up on a non-default port (not 1433), I am unable to establish a connection unless I specify the port number. This might seem normal
at first, but when my colleagues establish a remote connection (I am in an office) they do not need to specify a port number. I've seen other questions posted on the forum related to the port number, but the difference is that our DB configuration works
for everyone except myself, thus it seems like a client side issue.
For example, "dbserver\instancename" works for everyone else, but fails for me unless I specify "dbserver\instancename,PortNum". This is true through SQL management studio, through code, or through anything.
So my question is, what should I look for on my machine as the culprit? At first glance, there is not much different between my machine and the others. We're all on Win 7, we use active directory, and we all seem to belong to the same groups
(give or take). My machine has much more installed in the way of dev tools (visual studio 2013, all of the dotnet frameworks, etc). The DB is SQL 2005.
I have no access to the DB server, nor will the DBAs help me troubleshoot--they claim it's a client side problem. So I am hoping I can isolate the problem on my end. Thanks in advance.

>Do you have any firewall configured on your machine? Here's how the the initial handshake happens
- when you try to connect to SQL Server named instance without specifying a port number, SQL send the information about port number back on the UDP port 1434 and then the connection succeeds. If your UDP port 1434 on the client is closed, the client connection
wouldn't know which port to connect to and will fail.
I've disabled all antivirus software and stopped the windows firewall service. No change.

How to get the name of a field without specifying it as a string (somehow v

Is it possible to get the name of a field (or method) somehow via the class in which it is declared?
The reason why I ask is, that quite often the name of a field is important, because the name is the anchor for further processing, like for example when using reflection (e.g. Class.getfield(NameOfTheField)).
Assume you have class FooSimple with the field String firstName.
Now you would do something like this:
Class<FooSimple> cls = FooSimple.class;
Field f = cls.getField("firstName");
The problem is, that the string firstName is kind of hard coded. When the name of the field in class FooSimple changes (e.g. to theFirstName), the invocation will not work anymore when you forget to change the string too.
I think it would be very helpful to have access to the name of the field directly via the class by doing something like this.
Class<FooSimple> cls = FooSimple.class;
Field f = cls.getField(FooSimple.firstName.fieldName);
The Java Compiler would then resolve FooSimple.firstName.fieldName to the string firstName. When later the name of the field is changed, the IDE would change the name everywhere where it is used. So if the name of the field would be changed to theFirstName the IDE would also change the statement to
Class<FooSimple> cls = FooSimple.class;
Field f = cls.getField(FooSimple.theFirstName.fieldName);
A technique like this would be in my opinion much more safety and more generic.
Any ideas?
Best Regards.

Well, I think the discussion is going in a wrong direction because the original issue was not to discuss if it is worth coding some helper classes or a framework or that like. Let me bring it back to my original point.
Basically you can reduce my original question to this:
Currently it is possible to use the reflection API on a class level without specifying the name of the class with a string constant.
My issue is, that I think it would be a nice extension for Java, if the same would be possible for field variables of a Java class. Currently the only way you can do this is by specifying the field variable with a string constant.
Let me bring some motivations which brought me to this issue.
Assume you have an entity bean which represents a DB table and you use Java Persistence (either JPA or something like Hibernate). Then you would have a class looking like this (very simple sample to make this reply shorter).
@Entity
@Table(name = "PERSON")
public class Person implements Serializable {
@Column(name = "NAME")
private String name;
// constructor, getter, setter, etc. not listed here
}The whole issue of the design of JPA is, that such entity beans represent the mapping between the object model and the DB model, the mapping is expressed with annotations.
Okay, now lets assume you write a query in Query Language, e.g.
String sql = select p from Person p where name = :name;name is the name of the field variable, :name is the parameter you later set with Query.setParameter method.
What is not so nice is the fact, that you use the name of the class and the name of the field variables hardcoded to construct the query. Now you could think that basically this information is part of your entity class. First you start with the name of the class (i.e. the table name) to decouple this hardcoding.
You could write instead:
String sql = select p from + Person.class.getSimpleName() + p where name = :name;This is really nice, because whenever you change the name of your Person class, this change happens automatically for the sql statement as well.
I think the next thoughts are obvious, now, since you have decoupled the hardcoded part of the name of the class, you would like to do the same for the names of the field variables. But now you are stuck, there is no way to do this using a similar technique like for the name of the class. Either you stay with the query as it is now, or, to make it a little bit better, you code string constants for the field variables and use them. This issue brought me to the point that I think it would be nice to have the possibility to get the name of a field variable in a similar way as you can get it for the name of the class.
Conceptually it is just to go one level deeper, i.e.
first level is to get the name of a class
second level is to get the name of the field variable of a class.
Another sample would be, if you want to code something by using reflection. You have perfectly access to the reflection API starting at the class level like Person.class.allTheNiceReflectionMethods. There is no need to specify the class first with a string constant first, you directly start with the class, you can even be generic and just work on the Class.class level and still have access to all these nice methods to get out the information you need.
But if you need to start with a very specific field variable (like in the sample above), you must go by using a string constant like Person.class.getDeclaredField(name).
So basically I think that there exist already millions of lines of Java code where a field variable is specified for further processing, especially in combination with the reflection functionality and everywhere the field variables are specified by these string constants in double quotes. I would assume, that everyone has the same problem, once changing the name of the field variable means to take care that also the content of the string which specifies the name of the field variable is changed.
I am wondering why one of the replies commented, why the name of a field variable is changed, it sounds to me that this is something which basically never happens. I dont know, I think that this happens actually quite often and thanks to all these nice IDEs and their rename feature this is usually no problem. From time to time names of classes change, name of field change, yes, they are often even completely rewritten, new field variables come in some are deleted, whatever it is. The way I currently can access the name of a class makes the code safer, because when I consequently go with Class.class.getSimpleName I always know, that when I rename the class all these statements are changed too If I delete such a class, I at least get a compile error.
My very simple issues is, that I think it would be nice to have the same comfort not only on a class level but also on the level of field variables, nothing more, nothing less.
To be honest, I have not browsed the forum yet if such an issue was already raised by other people (I will do this now), but somehow it is hard to imagine, that I am the first one.
Best regards.

1.5.4 ora-00904 when opening a package from the connections navigator

Hi
I downloaded 1.5.4 for windows and immediately checked to see if this long standing bug has been fixed
1.5.0.53 New file types not opened as plsql (and now neither a
However it hasn't so next thing I do is go the connections navigator to open a package which is the workaround for the above bug (any update on when that is going to be fixed would be appreciated).
If I double click to open a package I get an error message
ORA-00904: "ATTRIBUTE": invalid identifier
A single click on a package does not give any error. Double clicking on the same package in 1.5.1 does not give any error message
Any ideas?
thanks
paul
Edited by: paul.schweiger on Mar 4, 2009 10:36 AM
Stupidly used the rich text editor which doesn't seem to work too well

JB,
There actually is a post from the team in this thread ;-)
The patch on 3/30 was not scheduled to fix any other errors other than the import issue we encountered. We included an LDAP fix and a 9i performance query issue. The exact bugs fixed are listed in the check for updates detail before you download the fix.
All bugs can be logged with Metalink, that is the primary place for logging and tracking bugs. The forum is for discussions on how to use the product - for pointers and advice.
Paul,
By your long standing bug, I assume you mean that .pks, pkb and .plb files are opened in the PL/SQL Editor. This has been fixed in 1.5.4.
What has not been done and has been scheduled for 2.0 is the ability to associate any extension with a file and then open that file with the pl/sql editor.
For all encountering the ora-00904 error, this is specifically related to opening PL/SQL in a 9i database and we have a bug logged for that.
Sue

Error when reopen USB connection without physical unplugging USB connection

Using Labview 8.5 to communicate with an USB device based on AT91SAM7S64 controller.
I has written a labview application that talks to several units and it works good as long as i dont close the USB connection
I wants the application to start talking to all USB devices that are already connected, at the moment i must reconnect all USB connection every time I start the Vi.
If a try to reopen a closed USB connection I got an timeout error when I read data from the device
to illustrate the problem I made a dummy test program. (Added as Attachment as jpg and vi)
Senario 1:
If i plug the USB connector into the computer and start the vi the first sequence works fine.
The second sequence fails.
Senario 2:
If i plug the USB connector into the computer and start the vi the first sequence works fine.
If i unplug and plug the USB connector between teh two sequences both works fine
Senario 3
If I remove the VISA close from the first sequence.
If i plug the USB connector into the computer and start the vi the first sequence works fine.
both sequences works fine without needing to unplug the USB connector.
Questions?
Does the VISA close command send a message to the USB device? can this be the reason for the need to replug the connection?
Does it exist a method to reopen a USB connection that has been closed?
All help is good help :-)
Attachments:
USB_error_example.jpg ‏101 KB
USB_error_Example.vi ‏30 KB

Hi Again,
I have tried to recreate the issue when using multiple runs of the same program but this time I have been unable to. Mine does manage to find the device again.
I have had a word with a few people and they have proposed a solution that would involve writing the references to the registry or a configuration file. They suggest:
First Run: The program will look to the registery/file to try and find the references. It wont find any so it will open the VISA references and write them to the registry. This should not close the references at the end of execution.
Run n : The program will look to the registry/file and find the references and use these for VISA operations.
First Run after Reboot: The program will look to the registry/file and find the references but will find that they are invalid so it will open new references and write these to registry for subsequent runs.
Functions for writing to the registry are under connectivity>>windows registry access VIs and have all the usual LabVIEW help files associated with them.
I hope this helps! let me know how it goes.
Message Edited by James McN on 08-07-2008 02:10 PM
James Mc
========
CLA and cRIO Fanatic
wiresmithtech.com/blog

MBPR display stays black when i try to swap from my HDMI TV back to inbuilt display - even when restarted without the HDMI cable connected

I am running OSX 10.8.2 on a month old MBP retina.
Detect display does not show up unless option key is pressed, and even then nothing happens when i click it - it seems to not recognise the inbuilt display at all. I have tried lots of combinations of sleep mode, restarts, CMD + OPT + P + R at start up, nothing will make my macbook display show up - the backlight lights up with a black screen at start up and then goes out. Have tried turning automatic graphics switching off also. Have done lots of research and found some other people with the same/similar problems but no solutions. Any help would be greatly appreciated as my Macbook is useless unless I am at the TV in my living room.

Hi Scotties123 - did you manage to solve this? I have the same problem :(

Ora 12154: TNS could not resolve connect identifier specified

Hi,
I have Oracle 11g (Release 1_32bit) Client on my C:\ drive which connect to a Remote 11g (11.1.0.7.0 - 64bit) server.
I have installed 10g DB Server(10.2.0.1.0) and Oracle 10g Forms(Forms [32 Bit] Version 10.1.2.0.2 ) on my D:\ drive.
When I try to connect to Oracle 10g DB from Forms using "Connect" button, I get following error:
"ORA-12154: TNS: could not resolve the connect identifier specified"
Tns and Listner files both are same in Developer_Suite home and 10g home.
Can someone please help me with this error?
Thanks

"ORA-12154: TNS: could not resolve the connect identifier specified"
$ oerr ora 12154
12154, 00000, "TNS:could not resolve the connect identifier specified"
// *Cause: A connection to a database or other service was requested using
// a connect identifier, and the connect identifier specified could not
// be resolved into a connect descriptor using one of the naming methods
// configured. For example, if the type of connect identifier used was a
// net service name then the net service name could not be found in a
// naming method repository, or the repository could not be
// located or reached.
// *Action:
//   - If you are using local naming (TNSNAMES.ORA file):
//      - Make sure that "TNSNAMES" is listed as one of the values of the
//        NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
//        (SQLNET.ORA)
//      - Verify that a TNSNAMES.ORA file exists and is in the proper
//        directory and is accessible.
//      - Check that the net service name used as the connect identifier
//        exists in the TNSNAMES.ORA file.
//      - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
//        file. Look for unmatched parentheses or stray characters. Errors
//        in a TNSNAMES.ORA file may make it unusable.
//   - If you are using directory naming:
//      - Verify that "LDAP" is listed as one of the values of the
//        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
//        (SQLNET.ORA).
//      - Verify that the LDAP directory server is up and that it is
//        accessible.
//      - Verify that the net service name or database name used as the
//        connect identifier is configured in the directory.
//      - Verify that the default context being used is correct by
//        specifying a fully qualified net service name or a full LDAP DN
//        as the connect identifier
//   - If you are using easy connect naming:
//      - Verify that "EZCONNECT" is listed as one of the values of the
//        NAMES.DIRETORY_PATH parameter in the Oracle Net profile
//        (SQLNET.ORA).
//      - Make sure the host, port and service name specified
//        are correct.
//      - Try enclosing the connect identifier in quote marks.
//   See the Oracle Net Services Administrators Guide or the Oracle
//   operating system specific guide for more information on naming.
$
Tns and Listner files both are same in Developer_Suite home and 10g home.Listener files are totally useless in Developer Suite home, since they are server files.

Abap import error DbSl Trace: ORA-1403 when accessing table SAPUSER

hi all
I am installing ERP 6.0 (ABAP) on win2003 cluster, oracle 10g, I have error at database instance intallation. here some logs
DD03L.log
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090812102157
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Apr 3 2009 09:03:56
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(RTF) ########## WARNING ###########
 Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
(TPL) ERROR: unknown template variable "tablespace"
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090812102157
import_monitor.log
ERROR: 2009-08-12 10:21:57 com.sap.inst.migmon.LoadTask run
Loading of 'DD03L' import package is interrupted with R3load error.
Process 'I:\usr\sap\PRD\SYS\exe\uc\NTAMD64\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error' exited with return code 2.
For mode details see 'DD03L.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2009-08-12 10:22:25
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-08-12 10:22:25
1 error(s) during processing of packages.
INFO: 2009-08-12 10:22:25
Import Monitor is stopped.
sapinst_dev.log
ERROR 2009-08-12 10:22:25.718
 CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
TRACE 2009-08-12 10:22:25.718 [iaxxejsbas.hpp:483]
 EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2009-08-12 10:22:25.734 [sixxcstepexecute.cpp:951]
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
TRACE 2009-08-12 10:22:25.781 [iaxxgenimp.cpp:752]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing service SAP ERP 6.0 Support Release 3 > SAP Systems > Oracle > High-Availability System > Based on AS ABAP > Database Instance( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You may now <ul> <li> choose Retry to repeat the current step. </li> <li> choose View Log to get more information about the error. </li> <li> stop the task and continue with it later. </li> </ul> Log files are written to C:\Program Files/sapinst_instdir/ERP/SYSTEM/ORA/HA/ABAP/DB. </body></html>
TRACE 2009-08-12 10:22:25.781 [iaxxgenimp.cpp:1255]
 CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
sapinst.log
WARNING 2009-08-12 10:22:25.718
Execution of the command "C:\j2sdk1.4.2_21-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_21"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_21-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_21-b03, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 26, failed 0, total 28.
Loading of 'DD03L' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28.
ERROR 2009-08-12 10:22:25.718
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-08-12 10:22:25.734
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|8|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
any idea
Regards
ABH

hi
All logs are above (include import_monitor.log and java)
thanks

MCOD Installation - Error ORA-1403 when accessing table SAPUSER

Hello.
We are in middle of a MCOD installation of 4.7 x 2.00 SR1 with BW 3.1 on Windows 2003/Oracle.
BW 3.1 is up and running, while 4.7 fails on R3loads.
Following are SAP000.log and SAPUSER.log files:
SAP000.log
===============================
D:\usr\sap\D11\SYS\exe\run/R3load.exe: START OF LOG: 20060507193904
D:\usr\sap\D11\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
D:\usr\sap\D11\SYS\exe\run/R3load.exe: version R6.40/V1.4
D:\usr\sap\D11\SYS\exe\run/R3load.exe -dbcodepage 1100 -i D:\Program Files\sapinst_instdir\R3E_472SR1_ABAP_NUC\DB/SAP0000.cmd -l D:\Program Files\sapinst_instdir\R3E_472SR1_ABAP_NUC\DB/SAP0000.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) ERROR: DDL statement failed
(DROP TABLE "REPOLOAD")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: ORA-406 occured when executing SQL statement (parse error offset = 0)
(DB) ERROR: DDL statement failed
(CREATE TABLE "REPOLOAD" ( "PROGNAME" VARCHAR2(40) DEFAULT ' ' NOT NULL , "R3STATE" VARCHAR2(1) DEFAULT ' ' NOT NULL , "MACH" NUMBER(5) DEFAULT 0 NOT NULL , "UNAM" VARCHAR2(12) DEFAULT ' ' NOT NULL , "UDAT" VARCHAR2(8) DEFAULT '00000000' NOT NULL , "UTIME" VARCHAR2(6) DEFAULT '000000' NOT NULL , "L_DATALG" NUMBER(10) DEFAULT 0 NOT NULL , "Q_DATALG" NUMBER(10) DEFAULT 0 NOT NULL , "SDAT" VARCHAR2(8) DEFAULT '00000000' NOT NULL , "STIME" VARCHAR2(6) DEFAULT '000000' NOT NULL , "MINOR_VERS" NUMBER(5) DEFAULT 0 NOT NULL , "MAJOR_VERS" NUMBER(10) DEFAULT 0 NOT NULL , "LDATA" BLOB , "QDATA" BLOB ) TABLESPACE PSAPD11620 STORAGE (INITIAL 0000000016K NEXT 0000040960K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 406)
error message returned by DbSl:
ORA-00406: COMPATIBLE parameter needs to be 9.2.0.0.0 or greater
(DB) INFO: disconnected from DB
D:\usr\sap\D11\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\D11\SYS\exe\run/R3load.exe: END OF LOG: 20060507193905
========================================
SAPUSER.log
==============================
D:\usr\sap\D11\SYS\exe\run/R3load.exe: START OF LOG: 20060507193834
D:\usr\sap\D11\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
D:\usr\sap\D11\SYS\exe\run/R3load.exe: version R6.40/V1.4
D:\usr\sap\D11\SYS\exe\run/R3load.exe -dbcodepage 1100 -i D:\Program Files\sapinst_instdir\R3E_472SR1_ABAP_NUC\DB/SAPUSER.cmd -l D:\Program Files\sapinst_instdir\R3E_472SR1_ABAP_NUC\DB/SAPUSER.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) INFO: disconnected from DB
D:\usr\sap\D11\SYS\exe\run/R3load.exe: job completed
D:\usr\sap\D11\SYS\exe\run/R3load.exe: END OF LOG: 20060507193835
==============================================
Kindly look into it.
Thanks
KT

Hi KT,
Actually the problem is not ORA-1403, but the ORA-00406: COMPATIBLE parameter needs to be 9.2.0.0.0 or greater.
Please update the COMPATIBLE parameter in your init<SID>.ora file and restart the database. This should fix your problem.
Kind regards,
Alexander Webster
P.S. points are appreciated if my reply was helpfull.
Message was edited by: Alexander Webster
Removed typo

ORA-1403 when accessing table SAPUSER

Hi all,
I was performed from Windows 2003 R2 32bit to Windows 2008 R2 64bit for Homogeneous system copy for SAP ERP 6.0 SR2.
I occure error during Importing on Windows 2008 R2 64bit using sapinst.exe of Install Master ERP 2005 SR2.
Source system : Windows 2003 R2 32bit + Oracle 10.2.0.2 + ERP 2005 SR2 with Non-Unicode
Target system : Windows 2008 R2 64bit + Oracle 10.2.0.5 + ERP 2005 SR2 with Non-Unicode
The step is stop "Import ABAP"
1. Error detail log
D:\usr\sap\MAR\SYS\exe\nuc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MAR\SYS\exe\nuc\NTAMD64\R3load.exe: version R7.00/V1.4
Compiled Jul 16 2007 22:44:14
D:\usr\sap\MAR\SYS\exe\nuc\NTAMD64\R3load.exe -dbcodepage 1100 -i test_MIGKEY.cmd -l test_MIGKEY.log -K
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(CNV) ERROR: rscpMCActivate rc = 2048
--------------------------------------5-
code: 2048 RSCPENOCONV
in character code "MDMP" unknown
module: rscpc location: 22 line: 14584
TSL01: F43 p3: MDMP
D:\usr\sap\MAR\SYS\exe\nuc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\MAR\SYS\exe\nuc\NTAMD64\R3load.exe: END OF LOG: 20140924032758
2. R3load test connection error
C:\Users\maradm.IDES>R3load.exe -testconnect
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
R3load.exe: START OF LOG: 20140924033549
R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
R3load.exe: version R7.00/V1.4
Compiled Jul 16 2007 22:44:14
R3load.exe -testconnect
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
(DB) INFO: disconnected from DB
R3load.exe: job completed
R3load.exe: END OF LOG: 20140924033549
C:\Users\maradm.IDES>
3. R3trans connect test error
C:\Users\maradm.IDES>R3trans -d .
This is R3trans version 6.14 (release 700 - 15.06.07 - 15:50:00).
2EETW000 sap_dext called with msgnr "2":
2EETW000 ---- db call info ----
2EETW000 function: db_ntab
2EETW000 fcode: NT_RDTDESCR
2EETW000 tabname: TADIR
2EETW000 len: 5
2EETW000 key: TADIR
2EETW000 retcode: 2
R3trans finished (0012).
trans.log
4 ETW000 [dev trc ,00000] SELECT USERID, PASSWD FROM SAPUSER WHERE USERID IN (:A0, :A1)
4 ETW000 393 0.034113
4 ETW000 [dbsloci. ,00000] *** ERROR => ORA-1403 when accessing table SAPUSER
4 ETW000 429 0.034542
4 ETW000 [dev trc ,00000] set_ocica() -> OCI or SQL return code 1403 14 0.034556
4 ETW000 [dev trc ,00000] Disconnecting from connection 0 ... 12 0.034568
4 ETW000 [dev trc ,00000] Rolling back transaction ... 10 0.034578
4 ETW000 [dev trc ,00000] Closing user session (con_hdl=0,svchp=000000000025BF58,usrhp=000000000AC98A60)
4 ETW000 221 0.034799
4 ETW000 [dev trc ,00000] Now I'm disconnected from ORACLE 413 0.035212
4 ETW000 [dev trc ,00000] Try to connect with default password 21 0.035233
4 ETW000 [dev trc ,00000] Connecting as SAPSR3/<pwd>@MAR on connection 0 (nls_hdl 0) ... (dbsl 700 250407)
4 ETW000 24 0.035257
4 ETW000 [dev trc ,00000] Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
4 ETW000 27 0.035284
4 ETW000 [dev trc ,00000] 0 WE8DEC 1 0000000000253E70 000000000025C098 00000000002640F8
4 ETW000 12 0.035296

Hi Vagesan,
Thank you for your reply
First i try to connection test via R3load -testconnect
 It is ok.
 This problem not correct password of SAPR3. so i modify table SAPUSER OF OPS$ schema. I refer to Note 400241 - Problems with ops$ or sapr3 connect to Oracle
Second.
I retry SAPINST gui of sapinst.exe with button "retry".
but this error message the below.
I guess this IDES System is MDMP codepage.
D:\usr\sap\MAR\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140924061219
D:\usr\sap\MAR\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MAR\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4
Compiled Jul 17 2007 00:40:17
D:\usr\sap\MAR\SYS\exe\uc\NTAMD64\R3load.exe -dbcodepage 4103 -i test_MIGKEY.cmd -l test_MIGKEY.log -K
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(CNV) ERROR: rscpMCActivate rc = 2048
--------------------------------------5-
code: 2048 RSCPENOCONV
in character code "MDMP" unknown
module: rscpc location: 22 line: 14584
TSL01: F43 p3: MDMP
D:\usr\sap\MAR\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\MAR\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140924061219

ORA-12154 could not resolve the connect indentifier specified

[http://www.freeimagehosting.net/image.php?793d240bb3.jpg]
when i try to install oracle 10g i find this problem i wish you help me

user473080 wrote:
[http://www.freeimagehosting.net/image.php?793d240bb3.jpg]
when i try to install oracle 10g i find this problem i wish you help meIn the future please work from a command line and use copy and paste to put commands and results in your posts. Many people's corporate nets block access to blog sites.
I have recently blogged extensively on this very subject. See edstevensdba.wordpress.com. I can't post a link to the exact article, because my corporate website blocks access to blog sites. I have also, many many times posted on this error in this forum, which a cursory search would have turned up. But once again, back by popular request:
=================================
ORA-12154: TNS:could not resolve the connect identifier specified
This error means one thing, and one thing only. The client could not find the specified entry in the tnsnames.ora file being used.
As a follow-on to that statement, remember that when you use a dblink, the database in which the link is defined is acting as a client to the database that is the target of the link. So in this case, the tnsnames.ora file on the host of your source should have an entry for your target db, as defined in the db_link.
And for the umpteenth time ... this error has NOTHING to do with the status of a listener. The connection request never got far enough to reach a listener. If anyone tells you to check a listener in response to ora-12154, they are not paying attention, or do not understand how TNS works. This error is the equivalent of not being able to place a telephone call because you don't know the number of the party you want to reach. You wouldn't debug that situation by going to the other guy's house and testing his telephone, or by going to the phone company and testing the switchboard. And you don't debug a ORA-12154 by checking the listener. If I had a top ten list of "Incredibly Simple Concepts (tm)" that should be burned into the brain of everyone who claims to be an Oracle DBA, it would include "ORA-12154 Has Nothing To Do With The Listener".
=================================
A couple of important points.
First, the listener is a server side only process. It's entire purpose in life is to receive requests for connections to databases and set up those connections. Once the connection is established, the listener is out of the picture. It creates the connection. It doesn't sustain the connection. One listener, with the default name of LISTENER, running from one oracle home, listening on a single port, will serve multiple database instances of multiple versions running from multiple homes. It is an unnecessary complexity to try to have multiple listeners or to name the listener as if it belongs to a particular database. That would be like the telephone company building a separate switchboard for each customer.
Additional notes on the listener: One listener is capable of listening on multiple ports. But please notice that it is the listener using these ports, not the database instance. You can't bind a specific listener port to a specific db instance. Similarly, one listener is capable of listnening on multiple IP addresses (in the case of a server with multiple NICs) But just like the port, you can't bind a specific ip address to a specific db instance.
Second, the tnsnames.ora file is a client side issue. It's purpose is for address resolution - the tns equivalent of the 'hosts' file further down the network stack. The only reason it exists on a host machine is because that machine can also run client processes.
Assume you have the following in your tnsnames.ora:
larry =
(DESCRIPTION =
 (ADDRESS_LIST =
 (ADDRESS = (PROTOCOL = TCP)(HOST = myhost)(PORT = 1521))
 (CONNECT_DATA =
 (SERVICE_NAME = curley)
)Now, when you issue a connect, say like this:
$> sqlplus scott/tiger@larrytns will look in your tnsnames.ora for an entry called 'larry'. Finding it, tns sends a request through the normal network stack to (PORT = 1521) on (HOST = myhost) using (PROTOCOL = TCP), asking for a connection to (SERVICE_NAME = curley).
Where is (HOST = myhost) on the network? When the request gets passed from tns to the next layer in the network stack, the name 'myhost' will get resolved to an IP address, either via a local 'hosts' file, via DNS, or possibly other less used mechanisms. You can also hard-code the ip address (HOST = 123.456.789.101) in the tnsnames.ora.
Next, the standard networking process delivers the message to port 1521 on myhost. Hopefully, there is a listener on myhost configured to listen on port 1521, and that listener knows about SERVICE_NAME = curley. If so, the listener will spawn a server process to act as the intermediary between your client and the database instance. Communication to the server process will be on a randomly selected available port. At that point the listener is out of the process and continues to user port 1521 to await other connection requests.
What can go wrong?
First, there may not be an entry for 'larry' in your tnsnames. In that case you get "ORA-12154: TNS:could not resolve the connect identifier specified" No need to go looking for a problem on the host, with the listener, etc. If you can't place a telephone call because you don't know the number (can't find your telephone directory (tnsnames.ora) or can't find the party you are looking for listed in it (no entry for larry)) you don't look for problems at the telephone switchboard.
Maybe the entry for larry was found, but myhost couldn't be resolved to an IP address (say there was no entry for myhost in the local hosts file). This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe there was an entry for myserver in the local hosts file, but it specified a bad IP address. This will result in "ORA-12545: Connect failed because target host or object does not exist"
Maybe the IP was good, but there is no listener running: "ORA-12541: TNS:no listener"
Maybe the IP was good, there is a listener at myhost, but it is listening on a different port. "ORA-12560: TNS:protocol adapter error"
Maybe the IP was good, there is a listener at myhost, it is listening on the specified port, but doesn't know about SERVICE_NAME = curley. "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor"
Third: If the client is on the same machine as the db instance, it is possible to connect without referencing tnsnames and without going through the listener.
Now, when you issue a connect, say like this:
$> sqlplus scott/tigertns will attempt to establish an IPC connection to the db instance. How does it know the name of the instance? It uses the current value of the enviornment variable ORACLE_SID. So...
$> export ORACLE_SID=fred
$> sqlplus scott/tigerIt will attempt to connect to the instance known as "fred". If there is no such instance, it will, of course, fail. Also, if there is no value set for ORACLE_SID, the connect will fail.
check executing instances to get the SID
[oracle@vmlnx01 ~]$ ps -ef|grep pmon|grep -v grep
oracle 4236 1 0 10:30 ? 00:00:00 ora_pmon_vlnxora1set ORACLE_SID appropriately, and connect
[oracle@vmlnx01 ~]$ export ORACLE_SID='vlnxora1
[oracle@vmlnx01 ~]$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:42:37 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsNow set ORACLE_SID to a bogus value, and try to connect
SQL> exit
[oracle@vmlnx01 ~]$ export ORACLE_SID=FUBAR
[oracle@vmlnx01 ~]$ sqlplus scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:42:57 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
Enter user-name: Now set ORACLE_SID to null, and try to connect
[oracle@vmlnx01 ~]$ export ORACLE_SID=
[oracle@vmlnx01 ~]$ sqlplus /scott/tiger
SQL*Plus: Release 10.2.0.4.0 - Production on Wed Sep 22 10:43:24 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-12162: TNS:net service name is incorrectly specifiedOk, that is how we get from the client connection request to the listener. What about the listener's part of all this?
The listener is very simple. It's job is to listen for connection requests and make the connection (server process) between the client and the database instance. Once that connection is made, the listener is out of the picture. If you were to kill the listener, all existing connections would continue. The listener is configured with the listener.ora file, but if that file doesn't exist, the listener is quite capable of starting up with all default values. One common mistake with the listner configuration is to specify "HOST=localhost" or "HOST=127.0.01". This is a NONROUTABLE ip address. LOCALHOST and ip address 127.0.0.1 always mean "this machine on which I am sitting". So, all computers are known as "localhost" or "127.0.0.1". If you specify this address, the listener will only be capable of receiving requests from the machine on which it is running. If you specified that address in your tnsnames file - on a remote client machine - the request would be routed to the machine on which the requesting client resides. Probably not what you want.
=====================================

Ora-12154 Could not resolve the connect Identifier specified

I am facing problem for communicating to Microsoft SQL Server through Oracle GateWay.
*1*. In installed Oracle Gateway 11.2 @D:\product\11.2.0\tg
*2. D:\product\11.2.0\tg\dg4msql\admin\initdg4msql.ora* is as:
HS_FDS_CONNECT_INFO=dba.Insignia
HS_FDS_TRACE_LEVEL=OFF
HS_FDS_RECOVERY_ACCOUNT=RECOVER
HS_FDS_RECOVERY_PWD=RECOVER
*3. listener.ora is as (D:\product\11.2.0\tg\NETWORK\ADMIN\tnsnames.ora)*
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dba)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
ADR_BASE_LISTENER = D:\product\11.2.0\tg
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = dg4dmssqldb)
(PROGRAM = D:\product\11.2.0\tg\bin\dg4msql)
SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF
*4. tnsnames.ora is as (D:\product\11.2.0\tg\NETWORK\ADMIN\listener.ora)*
PROD=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.0.230)(PORT=1521))
(CONNECT_DATA=(SID=PROD))
msql1=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=dba)(PORT=1521))
(CONNECT_DATA=
(SID=dg4dmssqldb) )
(HS=OK)
*5. Oracle Database Link (its working well)*
create database link apps connect to dba identified by dba using 'prod';
*6. Microsoft Sql server Database Link*
create database link msql1 connect to "sa" identified by "angal" using 'msql1' ;
When i try to select data through microsoft sql server database link its show following error;
Ora-12154 Could not resolve the connect Identifier specified
Wher i wrong......

Hello,
I have not used Oracle Gateway for a long time, but did you try to rename the file D:\product\11.2.0\tg\dg4msql\admin\initdg4msql.ora into D:\product\11.2.0\tg\dg4msql\admin\initdg4dmssqldb.ora ?
initdg4msql.ora is the default name, and should be changed if you do not use dg4msql as gateway SID:
http://download.oracle.com/docs/cd/E11882_01/gateways.112/e12013/configsql.htm#autoId2
Hope it will help.
Regards,
Sylvie

Ora-12154 when trying to connect to database from fortran application

I am trying to connect to database and run an simple select query to a table(without any where clause) using pro*fortran code.
the connect strng is like
exec sql connect :uidpwd
where uidpwd = username/password@SID
SID and tnsnames connect string are the same.
The fortran (profortran) code is placed in the database server and there are no errors when make is run.
Tnsping is working fine, also i am able to conect using sql*plus and run the same query.
Please help
Thanks and Regards
Nitin

Hi Nitin
Thanks for the helpful! With your point I'm now Pro! Great thanks.
By the way have your seen that?
Files such as LISTENER.ORA, TNSNAMES.ORA, SQLNET.ORA, if configured manually, or copied and edited from earlier releases of Oracle Database may have record attributes that are incompatible with Oracle Database 10g release 2. The software cannot read such files. The required record format is stream_lf and the record attributes are carriage_control and carriage_return.
This may result in:
Inability to start the listener
Services not registered with the listener
Inability to connect to other databases
ORA-12154: TNS:could not resolve service name
Run the following command on each file affected:
$ DIR/FULL filename
An output similar to the following may be displayed:
Record format: Variable length, maximum 255 bytes
Record attributes: Carriage return carriage control
If the output includes the preceding entries, then run the following command:
$ CONVERT/FDL=SYS$INPUT filename filename
RECORD
CARRIAGE_CONTROL CARRIAGE_RETURN
FORMAT STREAM_LF
^Z
Otherwise herewith an interesting metalink note. Doc ID: Note:437597.1
Subject: Ora-12154 When Executing Pro*Fortran Code Compiled With Oracle 10g.
Hope this will also help you...
Cheers
Hubert

ORA-12154: TNS:could not resolve the connect identifier specified (sqlplus)

Hi All,
I don't know if this has ever been posted, but since I've spent a week figuring it out (no joke, a week), I thought I would post it so that no one else has to waste this much time.
"ORA-12154: TNS:could not resolve the connect identifier specified" from what I've seen on this site is a major problem for a lot of people, but I did not find a reference to my specfic problem.
FYI--
My Database is called "ordidm"
userID: SYSMAN
password: p@ssw0rd
My specific issue was the following:
I can....
- Connect to the database via the client "admin assstant" GUI in Windows while supplying the userID and password using the "Database Authentication".
- Connect via sqlplus as "/as sysdba"
- "tnsping oraidm" passes works just fine.
I CANNOT....
- connect to oraidm at the dos prompt by using sqlplus, regardless of whether or not I supply all the user authentiocation information and db name on one line, or...if I just type "sqlplus" at the command prompt and then enter the userID and password when prompted. Every time I get the "ORA-12154: TNS:could not resolve the connect identifier specified" error message.
Ready for this?? (some may have guessed this already) The problem is the "@" in my password. After looking closely at the trace logs, I noticed that one of the entries was...
[09-MAR-2009 08:23:12:921] nnftrne: Original name: ssw0rd
Remember that the format for connecting on one line at the dos prompt is
C:/> sqlplus SYSMAN/p@ssw0rd oraidm
or you can do the following...
C:\Documents and Settings\Administrator.WIN2K3>sqlplus
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Mar 9 09:08:50 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: scott
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL>
(BTW-I just started using the "scott" ID because from what I understand, changing the SYSMAN userID password is kind of a pain. Figured just using "scott" ID would be easier to test)
So of course what it's doing is counting everything after the first "@" as the database name...which of course it can't find in the tnsnames.ora file. Also, contrary to some other posts I found here and there, enclosing the userID and/or passowrd in quotes does not do any good. Apparently, even when using the 2nd method...in the background, the end result is it must pass the whole thing as one long string much like in the 1st method (as you will get the same truncated "Original Name" of "ssw0rd" in the log)
So...the question is, why does Oracle even allow "@" in the password if it will become an issue with sqlplus??? Also, if you can't (or shouldn't) use it, why isn't it documented somewhere? At the least I would expect the installer to at least warn you ahead of time that an "@" is not suggested. I don't remember it being there. Maybe it's just me and I'm just missing this info somewhere
I sincerely hope this saves someone else a week of their life. ;-)
-Eric

user8100001 wrote:
Hi All,
I don't know if this has ever been posted, but since I've spent a week figuring it out (no joke, a week), I thought I would post it so that no one else has to waste this much time.
"ORA-12154: TNS:could not resolve the connect identifier specified" from what I've seen on this site is a major problem for a lot of people, but I did not find a reference to my specfic problem.
FYI--
My Database is called "ordidm"
userID: SYSMAN
password: p@ssw0rdThere are restrictions from oracle side how should password look:
Passwords can be from 1 to 30 characters.
The first character in an Oracle password must be a letter.
Only letters, numbers, and the symbols “#”, “_” and “$” are acceptable in a password.
And password must not be a reserved word (look into v$reserved_words).
And as You can see sysman password containt "@" - this is not allowed.
>
My specific issue was the following:
I can....
- Connect to the database via the client "admin assstant" GUI in Windows while supplying the userID and password using the "Database Authentication".
- Connect via sqlplus as "/as sysdba"
- "tnsping oraidm" passes works just fine.
I CANNOT....
- connect to oraidm at the dos prompt by using sqlplus, regardless of whether or not I supply all the user authentiocation information and db name on one line, or...if I just type "sqlplus" at the command prompt and then enter the userID and password when prompted. Every time I get the "ORA-12154: TNS:could not resolve the connect identifier specified" error message.
Ready for this?? (some may have guessed this already) The problem is the "@" in my password. After looking closely at the trace logs, I noticed that one of the entries was...
[09-MAR-2009 08:23:12:921] nnftrne: Original name: ssw0rd
Remember that the format for connecting on one line at the dos prompt is
C:/> sqlplus SYSMAN/p@ssw0rd oraidAnd here You can see why this symbol is restricted as full syntax for sqlplus in this case will be:
sqlplus username/password@oraidm
but in Your case @symbol already is in password.
Here can be used a small trick
sqlplus sysman/"p@ssw0rd"@oraid
>
or you can do the following...
C:\Documents and Settings\Administrator.WIN2K3>sqlplus
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Mar 9 09:08:50 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter user-name: scott
Enter password:
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL>
(BTW-I just started using the "scott" ID because from what I understand, changing the SYSMAN userID password is kind of a pain. Figured just using "scott" ID would be easier to test)
So of course what it's doing is counting everything after the first "@" as the database name...which of course it can't find in the tnsnames.ora file. Also, contrary to some other posts I found here and there, enclosing the userID and/or passowrd in quotes does not do any good. Apparently, even when using the 2nd method...in the background, the end result is it must pass the whole thing as one long string much like in the 1st method (as you will get the same truncated "Original Name" of "ssw0rd" in the log)
So...the question is, why does Oracle even allow "@" in the password if it will become an issue with sqlplus??? Also, if you can't (or shouldn't) use it, why isn't it documented somewhere? At the least I would expect the installer to at least warn you ahead of time that an "@" is not suggested. I don't remember it being there. Maybe it's just me and I'm just missing this info somewhereActually Oracle is not allowing this if You will just try to
alter user scott identidified by p@ssword
You will get error message (ORA-00922: missing or invalid option), but You can
alter user scott identified by "p@ssword" - and that will work.
These double quotes will allow to overide Oracle restrictions.

ORA-12546 When connecting without specifying sid in connect string

Similar Messages

Maybe you are looking for