Question:
Hi Basis Guys,
At the time of DB export, it throws the error in R3ldctlExport.log says :
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154
DbSl Trace: CONNECT failed with sql error '12154'
I was mentioned the path /tmp_cd. It consists of DB exports CD's in the name of Disk1...Disk7
Thanx in Advance.
Regards
Mano
Answer:
Mano, or anyone , I am having this same error. If possible, could you please post the solution?
Thanks!
Answer:
Hi,
Check your environmental variables it cannot connt to the database.
the error points to tnsnames.ora and listener.ora
Mark
_________________
Common sense is instinct, and enough of it is genius
Answer:
Thanks for the hint, I'll compare the variables against our 4.6 IDES system. So frustrating that there is no installation guide for Enterprise IDES
Cheers
Answer:
Confirmed all my environment variables and still no luck. I must be missing something really simple, but am quite stuck at the moment.
Of course, being somewhat of a novice on the basis side doesn't help me, I apologize in advance for that and please have patient with my long explanation below!
Here is a breakdown of what I have tried, hopefully someone can assist
1. Oracle 9.2.0.5 installed on Win2K, home is c:\oracle\920\<sid>
2. All other environment related tasks completed (setting virutal memory, etc..).
3. SAP IDES 4.7 DVD's copied to the following structure on d: drive:
D:\DB_EXPORT\EXPORT1
D:\DB_EXPORT\EXPORT2
D:\DB_EXPORT\EXPORT3
D:\DB_EXPORT\EXPORT4
D:\DB_EXPORT\EXPORT5
D:\DB_EXPORT\EXPORT6
D:\DB_EXPORT\EXPORT7
Also contained in the directory D:\DB_EXPORT, are the following files:
3. SAPInst was executed and installed, first choice was "Install Server Components". This was done so successfully (specifying RAM, instance number, SID, etc....), logged off, loged back on, all env. variables seem to be set, all oracle services can be started, and SAP MMC is up and runnning (but not started of course).
4. SAPInst was exected again, into another directory, and second choice "Export Database Content" was chosen. All system variable are entered (sid, system number, schema, etc..), and then this is were it all goes to the birds.
You are then prompted for Database Source and Target System Parameters.
The Database Source System Parameters are greyed out, and contain your oracle home info, etc..
The Database Target System Parameters are open for input: Source DB dropdown box is changed from SAPDB to ORA, and the "target directory", which I ASSUME is actually the location of the Export DVD/CD's (shown in the above directory structure) allows you to specify a directory.
IF I choose the the D:\DB_EXPORT directory, the installation fails right away saying it cannot delete the LABEL.ASC file. I have attached the install log below under the heading ERROR#1 below (hopefully to make this message body more readable).
IF I choose another directory, such as D:\DATA, it creates the directories DB.. and it's subdirectories, and then errors out on the following error ..this was the original error that started this posting. Again, this error is located below under the heading ERROR#2.
I have tried all combinations and permutations with no luck. I am hoping that there is just something really simple that I am missing, as you know how some of these things are almost hard-coded, etc.
As mentioned previously, if it is an oracle problem, I am unsure of how to troubleshoot, as everything seems to be fine on the oracle side.
Any help or hints would be so greatly appreciated,
Thanks to all in advance!
ERROR#1 (note: this was the second time I had tried this, thus why the
**********************************************************
log say's "...already created...)
PHASE 2004-08-20 07:50:41
Prepare database export
INFO 2004-08-20 07:50:42
Copying file C:/SAPinst SAP EXPORT 1/keydb.xml to: C:/SAPinst SAP EXPORT 1/keydb.1.xml.
INFO 2004-08-20 07:50:42
Creating file C:\SAPinst SAP EXPORT 1\keydb.1.xml.
INFO 2004-08-20 07:50:42
Copying file C:/SAPinst SAP EXPORT 1/OraVolatileDatabaseParameters.xml to: C:/SAPinst SAP EXPORT 1/OraVolatileDatabaseParameters.1.xml.
INFO 2004-08-20 07:50:42
Creating file C:\SAPinst SAP EXPORT 1\OraVolatileDatabaseParameters.1.xml.
INFO 2004-08-20 07:50:42
File system node D:\DB_EXPORT/DB exists already. Nothing to do.
INFO 2004-08-20 07:50:42
File system node D:\DB_EXPORT/DATA exists already. Nothing to do.
INFO 2004-08-20 07:50:42
File system node D:\DB_EXPORT/DB/ADA exists already. Nothing to do.
INFO 2004-08-20 07:50:42
File system node D:\DB_EXPORT/DB/DB2 exists already. Nothing to do.
INFO 2004-08-20 07:50:42
File system node D:\DB_EXPORT/DB/DB4 exists already. Nothing to do.
INFO 2004-08-20 07:50:42
File system node D:\DB_EXPORT/DB/DB6 exists already. Nothing to do.
INFO 2004-08-20 07:50:42
File system node D:\DB_EXPORT/DB/INF exists already. Nothing to do.
INFO 2004-08-20 07:50:42
File system node D:\DB_EXPORT/DB/MSS exists already. Nothing to do.
INFO 2004-08-20 07:50:42
File system node D:\DB_EXPORT/DB/ORA exists already. Nothing to do.
INFO 2004-08-20 07:50:42
Processing of all file system node operations of table T_DBEXPORTDIR succeeded.
INFO 2004-08-20 07:50:42
Removing file D:/DB_EXPORT/LABEL.ASC.
ERROR 2004-08-20 07:50:42
FSL-02040 Unable to delete node D:/DB_EXPORT/LABEL.ASC with type file: Permission denied
ERROR 2004-08-20 07:50:42
FJS-00012 Error when executing script.
ERROR#2
**********************************************************
PHASE 2004-08-20 08:01:58
Prepare database export
INFO 2004-08-20 08:01:58
Copying file C:/SAPinst SAP EXPORT 3/keydb.xml to: C:/SAPinst SAP EXPORT 3/keydb.1.xml.
INFO 2004-08-20 08:01:58
Creating file C:\SAPinst SAP EXPORT 3\keydb.1.xml.
INFO 2004-08-20 08:01:59
Copying file C:/SAPinst SAP EXPORT 3/OraVolatileDatabaseParameters.xml to: C:/SAPinst SAP EXPORT 3/OraVolatileDatabaseParameters.1.xml.
INFO 2004-08-20 08:01:59
Creating file C:\SAPinst SAP EXPORT 3\OraVolatileDatabaseParameters.1.xml.
INFO 2004-08-20 08:01:59
File system node D:\/DB exists already. Nothing to do.
INFO 2004-08-20 08:01:59
File system node D:\/DATA exists already. Nothing to do.
INFO 2004-08-20 08:01:59
File system node D:\/DB/ADA exists already. Nothing to do.
INFO 2004-08-20 08:01:59
File system node D:\/DB/DB2 exists already. Nothing to do.
INFO 2004-08-20 08:01:59
File system node D:\/DB/DB4 exists already. Nothing to do.
INFO 2004-08-20 08:01:59
File system node D:\/DB/DB6 exists already. Nothing to do.
INFO 2004-08-20 08:01:59
File system node D:\/DB/INF exists already. Nothing to do.
INFO 2004-08-20 08:01:59
File system node D:\/DB/MSS exists already. Nothing to do.
INFO 2004-08-20 08:01:59
File system node D:\/DB/ORA exists already. Nothing to do.
INFO 2004-08-20 08:01:59
Processing of all file system node operations of table T_DBEXPORTDIR succeeded.
INFO 2004-08-20 08:01:59
Removing file D:/LABEL.ASC.
INFO 2004-08-20 08:01:59
Creating file D:\LABEL.ASC.
PHASE 2004-08-20 08:02:01
Database Export
INFO 2004-08-20 08:02:01
Creating file C:\SAPinst SAP EXPORT 3\R3ldctl.exe.log.
INFO 2004-08-20 08:02:04
Changed working directory to C:\SAPinst SAP EXPORT 3.
INFO 2004-08-20 08:02:22
See 'D:\usr\sap\DWS\SYS\exe\run/R3ldctl.exe -l ./R3ldctlExport.log -p D:\/DATA/ ' output in 'C:\SAPinst SAP EXPORT 3\R3ldctl.exe.log'.
ERROR 2004-08-20 08:02:22
MOS-01012 PROBLEM: 'D:\usr\sap\DWS\SYS\exe\run/R3ldctl.exe -l ./R3ldctlExport.log -p D:\/DATA/ ' returned with '2' which is not a defined as a success code.
ERROR 2004-08-20 08:02:22
FJS-00012 Error when executing script.
Answer:
Hi,
Firstly download the latest R3ldctl from SAPNet
Read note 516246.... though in the note it references SAP DB about your error,it will give you an idea of what the error is about...
Mark
_________________
Common sense is instinct, and enough of it is genius
Answer:
As mentioned previously, if it is an oracle problem, I am unsure of how to troubleshoot, as everything seems to be fine on the oracle side.
check if your oracle listener is running.
also try:
R3trans -d
Snowy
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759
Answer:
Thanks for your suggestions Mark and Snowy.
Downloded and utilized the new R3ldctl, but still the same error.
Then tried R3TRANS but it also cannot connect:
This is r3trans version 6.07 (release 620 - 05.08.02 - 15:04:42).
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'DWS'"
r3trans finished (0012).
Made sure the oracle listener was started, also restarted it to make sure. One thing I did notice, was that of the 5 Oracle services and 2 SAP services, both SAP services were running, and only the OracleDWS920Agent and OracleDWS920Listener were started. Wasn't sure if this was correct.
Anywho, based on the above, any other things I can try. Will continue to research on the web in the meanwhile.
Thanks again to all.
PS: Here is the full error log for R3ldctl exports attempt:
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154
DbSl Trace: CONNECT failed with sql error '12154'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154
DbSl Trace: CONNECT failed with sql error '12154'
ERROR: DbSlConnect rc= 99
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154
DbSl Trace: CONNECT failed with sql error '12154'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154
DbSl Trace: CONNECT failed with sql error '12154'
Answer:
provide tnsnames.ora and listener.ora
also:
open a command prompt
type:
SET
provide results.
Snowy
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759
Answer:
Here you go. Can't thank you enough for lending a hand
Anything catch your eye?
tnsnames.ora content:
# TNSNAMES.ORA Network Configuration File: C:\Oracle\DWS\920\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
)
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)
listener.ora content:
# LISTENER.ORA Network Configuration File: C:\Oracle\DWS\920\network\admin\listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = devsapent)(PORT = 1521))
)
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\Oracle\DWS\920)
(PROGRAM = extproc)
)
)
all variables from set command:
C:\Documents and Settings\Administrator>set
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\Administrator\Application Data
CommonProgramFiles=C:\Program Files\Common Files
COMPUTERNAME=DEVSAPENT
ComSpec=C:\WINNT\system32\cmd.exe
DBMS_TYPE=ORA
DBS_ORA_SCHEMA=SAPDWS
dbs_ora_tnsname=DWS
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\Administrator
JAVA_HOME=C:\Program Files\Java\j2re1.4.2_05\
LOGONSERVER=\\DEVSAPENT
NLS_LANG=AMERICAN_AMERICA.WE8DEC
NUMBER_OF_PROCESSORS=1
ORACLE_HOME=C:\Oracle\DWS\920
ORACLE_SID=DWS
OS=Windows_NT
Os2LibPath=C:\WINNT\system32\os2\dll;
Path=C:\Oracle\DWS\920\jre\1.4.2\bin\client;C:\Oracle\DWS\920\jre\1.4.2\bin;C:\O
racle\DWS\920\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\
jre\1.1.8\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;D:\usr\sap\DWS\S
YS\exe\run
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 8, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=0208
ProgramFiles=C:\Program Files
PROMPT=$P$G
SAPLOCALHOST=devsapent
SystemDrive=C:
SystemRoot=C:\WINNT
TEMP=C:\WINNT\TEMP
TMP=C:\WINNT\TEMP
USERDOMAIN=DEVSAPENT
USERNAME=Administrator
USERPROFILE=C:\Documents and Settings\Administrator
windir=C:\WINNT
Answer:
this is what I thought, you have no entries in your listener for your instance. Try this (change bold entried with yours)
===========
# LISTENER.ORA Network Configuration File: F:\Oracle\SID\920\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC2))
)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = ZZZZZZ)(PORT = 1521))
)
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = ZZZZZZ)(PORT = 1527))
)
)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = F:\Oracle\SID\920)
(PROGRAM = extproc)
)
(SID_DESC =
(GLOBAL_DBNAME = SID)
(ORACLE_HOME = F:\Oracle\SID\920)
(SID_NAME = SID)
)
)
======
# TNSNAMES.ORA Network Configuration File: F:\Oracle\SID\920\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.
INST1_HTTP =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = ZZZZZZ)(PORT = 1521))
)
(CONNECT_DATA =
(SERVER = SHARED)
(SERVICE_NAME = MODOSE)
(PRESENTATION = http://HRService)
)
)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC2))
)
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)
SID.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = ZZZZZZ)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = ZZZZZZ)(PORT = 1527))
)
(CONNECT_DATA =
(SID = SID)
(SERVER = DEDICATED)
)
)
_________________
SapFans Moderator
NetWeaver ‘04–SAP Web AS for ORACLE certified
Search: /forums/search.php
SAP Notes: http://service.sap.com/notes
SAP Help: http://help.sap.com
Basic Rules: /forums/viewtopic.php?t=222759
Answer:
Hi Snowy; Applied your changes above, rebooted, and started all the Oracle services, but the OracleDWS920TNListener could not be started (does not give any useful information on the pop-up window).
I have double and triple checked that I created the file correctly as you supplied above.
Not sure if there is anything else I can try?
Thanks again,
Greg
Answer:
Not sure if this would make a difference, but I found a "sample" listener.ora file on the 4.7 IDES installation CD, it looks very similar in structure to that of the 4.6 IDES server. Wasn't sure if this was due to 4.6 being on 8.1.7 and 4.7 being on 9.2.0.5. Anyways, below is the sample:
################
# Filename......: listener.ora
# Created.......: created by SAP AG, R/3 Rel. >= 6.10
# Name..........:
# Date..........:
################
@LISTENER_NAME@ =
(ADDRESS_LIST =
(ADDRESS =
(PROTOCOL = @PROTOCOL_IPC@)
(KEY = @DB_SID@.WORLD)
)
(ADDRESS=
(PROTOCOL = @PROTOCOL_IPC@)
(KEY = @DB_SID@)
)
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = @PROTOCOL_TCP@)
(HOST = @HOST@)
(PORT = @PORT@)
)
)
STARTUP_WAIT_TIME_@LISTENER_NAME@ = @STARTUP_WAIT_TIME@
CONNECT_TIMEOUT_@LISTENER_NAME@ = @CONNECT_TIMEOUT@
TRACE_LEVEL_@LISTENER_NAME@ = @TRACE_LEVEL@
SID_LIST_@LISTENER_NAME@ =
(SID_LIST =
(SID_DESC =
(SDU = @SDU@)
(SID_NAME = @DB_SID@)
(ORACLE_HOME = @ORACLE_HOME@)
)
)
Answer:
Used the listener.ora and tnsnames.ora templates that were provided on the IDES install CD, and the listener is back up and running, BUT, same problem exists during the export install.
Taking a step back, it sure seems like a step is missing in the IDES installation to this point. A) Install Oracle with the "standard" options (note: believe "No" was chosen at the last step when it asked to created the database... same as in 4.6 IDES), B) install Oracle patches, C) prepare IDES export cd's on hard drive, D) use SAPInst to install "Server Components", E) use SAPInst to perform "Export Database Contents".
Due to the absence of an actual 4.7 IDES instalation guide, I have the feeling that something has been missed, either using a certain "hard coded" directory for say the export CD's, how/if utilization of some of the other "install" files on the SAPInst CD are supposed to be utilized, and if so how (some of these include OraVolatileDatabaseParameters.xml,
PROTOCOL.ORA, INITSID.ORA, LISTENER.ORA, TNSNAMES.ORA), etc...., or who knows what.
One would think that I would have had to miss a pretty big step to be having this problem, due to to the somewhat straightforward nature of the 4.6 IDES install, else wouldn't numerous other 4.7 IDES install's be having the same?
Then again, it might just be solar rays
/g
Answer:
When you use SAP IDES Ent. with a MCOD database,
Database system ID might be defferent from SAP system ID.
Input data as following guides...
1.SAPSystem ID : input SAP system ID (eg. R3E)
2.Database System ID : input database system ID (eg. SDB)
-> I think, if you input SAP system ID as a database system ID, SAPInst recognize that tha database system ID is your SAP system ID. So, SAPinst will try to connect database "R3E" which has information that listener does not support. Actually, in this case, SAPInst has to connect to database "SDB".
3..... input as you know.
The last window would request password of user 'sdbadm'. It's so strange..but ignore it and continue to installation. an error ora-01451 will be occurred, then click "OK" and terminate installation.
Now, you have to edit KEYDB.XML.
Open KEYDB.XML which is in <SAPInst DIR> using notepad and search "sdbadm" and replace "sdbadm" to "re3adm". Save file and exit. that's all.
Try again installation. You can find the SAPInst is working without error.
I guess... this is a bug on installation script or SAP's intention. Anyway we did solve the problem.
Cheers!
_________________
Cheers!
Regards.
Yoo,yoonjin.
Email:trueluck@korea.com
MSN:happytrueluck@hotmail.com
Tel.:82-11-9942-0069