on 10-26-2009 10:14 PM
Any advice on the error
O/S AIX 6.1
Oracle 10.2.0.4 with all the one-off patches
This is okay...
srddb01:srdadm 60> R3trans -x
This is R3trans version 6.13 (release 640 - 26.05.09 - 10:25:00).
unicode enabled version
R3trans finished (0000).
This is NOT okay...
srddb01:srdadm 61> R3trans -d
This is R3trans version 6.13 (release 640 - 26.05.09 - 10:25:00).
unicode enabled version
2EETW000 sap_dext called with msgnr "2":
2EETW000 -
db call info -
2EETW000 function: db_ntab
2EETW000 fcode: NT_RDTDESCR
2EETW000 tabname: TADIR
2EETW000 len (char): 5
2EETW000 key: TADIR
2EETW000 retcode: 2
R3trans finished (0012).
This does NOT work ...
startsap
Checking SRD Database
-
ABAP Database is not available via R3trans
Starting SAP-Collector Daemon
-
15:12:25 26.10.2009 LOG: Effective User Id is root
***********************************************************************
This is Saposcol Version COLL 20.87 640 - AIX v4.20 5L-64 bit 040309
Usage: saposcol -l: Start OS Collector
saposcol -k: Stop OS Collector
saposcol -d: OS Collector Dialog Mode
saposcol -s: OS Collector Status
The OS Collector (PID 843962) is already running .....
************************************************************************
saposcol already running
Running /usr/sap/SRD/SYS/exe/run/startdb
Trying to start SRD database ...
Log file: /home/srdadm/startdb.log
/usr/sap/SRD/SYS/exe/run/startdb: Terminating with error code 12
DB startup failed
vi /home/srdadm/startdb.log
-
Mon Oct 26 15:12:34 MST 2009
Connect to the database to verify, that the database is now open
R3trans check finished with return code: 12
ERROR: Startup of database failed
Notify Database Administrator.
/usr/sap/SRD/SYS/exe/run/startdb: Terminating with error code 12
~
Hi Bill,
Are you able to start the Database from sqlplus?
If you are trying to perform a system copy from another system, maybe you forgot to change the variable u201Cdbs_ora_schemau201D.
Please check the note u201CNote 534765 - db connect fails because of wrong db schema in environmentu201D
Another possible reason for your problem is that you forgot to create/change the OPS$ oracle account.
Please check note u201CNote 361641 - Creating OPS$ users on UNIXu201D.
Regards,
Federico Biavati
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> Are you able to start the Database from sqlplus?
The database is started already, otherwise he wouldn't get an error from the database interface layer.
His problem is, that R3trans tries to interpret a reply from a too new database version that is not properly handled by the database client software --> his Oracle client is too old.
Markus
Hello Bill,
you didn't tell us anything about your Oracle client version.
And before you ask: It's difficult to find out, if you don't happen to remember what you installed.
If you are not sure, let me suggest you follow Markus's advice, he clearly pointed out what your options are.
If your old client was working with Oracle 10.2.0.2, then, well, maybe you were just lucky. There is no guarantee that it will work with Oracle 10.2.0.4 as well.
regards
Hi Bill,
Just to confirm , can you check your lisnter is running state or not.
Thanks
Anil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
> This is NOT okay...
> srddb01:srdadm 61> R3trans -d
> This is R3trans version 6.13 (release 640 - 26.05.09 - 10:25:00).
> unicode enabled version
> 2EETW000 sap_dext called with msgnr "2":
> 2EETW000 -
db call info -
> 2EETW000 function: db_ntab
> 2EETW000 fcode: NT_RDTDESCR
> 2EETW000 tabname: TADIR
> 2EETW000 len (char): 5
> 2EETW000 key: TADIR
> 2EETW000 retcode: 2
> R3trans finished (0012)
What Oracle client do you use?
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you do not use a 640_EX2 kernel then you don't use the Oracle 10g instantclient.
The kernel is dependent on the Oracle client version it was linked with. So if you use the standard 640 kernel, then you use the Oracle 9.2 client. That works and is supported but only if you use the latest Oracle client 9.2.0.8.
Check the output of
disp+work -V
if 640_EX2 is not listed I would
- either download and install the latest Oracle client 9.2.0.8 and install it it /oracle/client or
- download and install a current 640_EX2 kernel and also download the latest instantclient for 10g
Markus
>
> 1) disp+work -V | grep 640_EX2
> This return nothing.
so you use the normal 640 kernel.
> 2) I am using Oracle 10.2.0.4
> Why do I need the Oracle 9.2.08 client?
The Oracle client needed is dependent on the SAP KERNEL version used, not on the database version used.
6.40 was developed before Oracle 10g was available so the Oracle 9.2 client was used to build that kernel; hence the 6.40 kernel depends during runtime on an Oracle client of version 9.2. So if you update the database you don't automatically use the newest client. To connect with a SAP kernel of 6.40 and Oracle client 9.2 to a 10g database you must use the client 9.2.0.8, older clients do not work and are not tested.
Check Note 1017418 - Installing Oracle 9208 Client software on UNIX
The other option is to install the 640_EX2 kernel, which is the same kernel as 640 with the difference that it used the new interface and the new Oracle instantclient. This is the recommended way. See
Note 1058988 - 640_EX2 Kernels
Note 819829 - Oracle Instant Client Installation and Configuration on Unix
Markus
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.