cancel
Showing results for 
Search instead for 
Did you mean: 

DB instance installation

Former Member
0 Kudos

Hi,

I've a problem during DB instance installation, the log file tells the following:

C:\usr\sap\TST\SYS\exe\run/R3load.exe: START OF LOG: 20090314010044

C:\usr\sap\TST\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP

C:\usr\sap\TST\SYS\exe\run/R3load.exe: version R6.40/V1.4 [UNICODE]

C:\usr\sap\TST\SYS\exe\run/R3load.exe -ctf I C:/51030431_4/DATA/SAP0000.STR C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/DDLORA.TPL C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAP0000.TSK ORA -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAP0000.log -o D

C:\usr\sap\TST\SYS\exe\run/R3load.exe: job completed

C:\usr\sap\TST\SYS\exe\run/R3load.exe: END OF LOG: 20090314010044

C:\usr\sap\TST\SYS\exe\run/R3load.exe: START OF LOG: 20090314085724

C:\usr\sap\TST\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP

C:\usr\sap\TST\SYS\exe\run/R3load.exe: version R6.40/V1.4 [UNICODE]

C:\usr\sap\TST\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAP0000.cmd -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAP0000.log -stop_on_error

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

C:\usr\sap\TST\SYS\exe\run/R3load.exe: job finished with 1 error(s)

C:\usr\sap\TST\SYS\exe\run/R3load.exe: END OF LOG: 20090314085732

C:\usr\sap\TST\SYS\exe\run/R3load.exe: START OF LOG: 20090314135536

C:\usr\sap\TST\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP

C:\usr\sap\TST\SYS\exe\run/R3load.exe: version R6.40/V1.4 [UNICODE]

C:\usr\sap\TST\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAP0000.cmd -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAP0000.log -stop_on_error

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

C:\usr\sap\TST\SYS\exe\run/R3load.exe: job finished with 1 error(s)

C:\usr\sap\TST\SYS\exe\run/R3load.exe: END OF LOG: 20090314135544

C:\usr\sap\TST\SYS\exe\run/R3load.exe: START OF LOG: 20090317181735

C:\usr\sap\TST\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP

C:\usr\sap\TST\SYS\exe\run/R3load.exe: version R6.40/V1.4 [UNICODE]

C:\usr\sap\TST\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAP0000.cmd -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\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): UTF8

(DB) INFO: REPOLOAD created #20090317181738

(DB) INFO: REPOLOAD~0 created #20090317181738

(DB) INFO: disconnected from DB

C:\usr\sap\TST\SYS\exe\run/R3load.exe: job completed

C:\usr\sap\TST\SYS\exe\run/R3load.exe: END OF LOG: 20090317181738

C:\usr\sap\TST\SYS\exe\run/R3load.exe: START OF LOG: 20090529102720

C:\usr\sap\TST\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP

C:\usr\sap\TST\SYS\exe\run/R3load.exe: version R6.40/V1.4 [UNICODE]

C:\usr\sap\TST\SYS\exe\run/R3load.exe -dbcodepage 4103 -i C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAP0000.cmd -l C:\Program Files\sapinst_instdir\R3E47X2\SYSTEM\ABAP\ORA\UC\DB/SAP0000.log -stop_on_error

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

DbSl Trace: OCI-call 'OCISessionBegin' failed: rc = 1034

DbSl Trace: CONNECT failed with sql error '1034'

(DB) ERROR: DbSlErrorMsg rc = 99

C:\usr\sap\TST\SYS\exe\run/R3load.exe: job finished with 1 error(s)

C:\usr\sap\TST\SYS\exe\run/R3load.exe: END OF LOG: 20090529102729

What is the problem ?

Regards

Accepted Solutions (1)

Accepted Solutions (1)

JPReyes
Active Contributor
0 Kudos

Read,

Note 491174 - Composite SAP note for ORA-01034

Regards

Juan

Former Member
0 Kudos

Hi,

I tried from command prompt (sqlplus startup) to start the database the error is the same:

Enter password:

ERROR:

ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

I also tried to stop and start from command prompt the listener as follows:

C:\Documents and Settings\Administrator>lsnrctl start

LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 29-MAY-2009 12:25

:33

Copyright (c) 1991, 2005, Oracle. All rights reserved.

Starting tnslsnr: please wait...

TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production

System parameter file is C:\oracle\product\10.2.0\db_1\network\admin\listener.or

a

Log messages written to C:\oracle\product\10.2.0\db_1\network\log\listener.log

Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\TST.WORLDip

c)))

Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\TSTipc)))

Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sapsrv)(PORT=1527)))

Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=TST.WORLD))

STATUS of the LISTENER

-


Alias LISTENER

Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Produ

ction

Start Date 29-MAY-2009 12:25:34

Uptime 0 days 0 hr. 0 min. 1 sec

Trace Level off

Security ON: Local OS Authentication

SNMP OFF

Listener Parameter File C:\oracle\product\10.2.0\db_1\network\admin\listener.o

ra

Listener Log File C:\oracle\product\10.2.0\db_1\network\log\listener.log

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\TST.WORLDipc)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\TSTipc)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sapsrv)(PORT=1527)))

Services Summary...

Service "TST" has 1 instance(s).

Instance "TST", status UNKNOWN, has 1 handler(s) for this service...

The command completed successfully

I started again the DB installation but the error is always the same:

*ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist*

What furthers action could I perform to solve ?

Regards

Former Member
0 Kudos

Hi,

also opened the file strdbs.cmd which contains:

@rem:: static char sccsid[] = "@(#) $Id: //bas/700_REL/src/krn/ntport/strdbsora.cmd#1 $ SAP";

@rem -


@rem Startup script for ORACLE database 8.x

@rem -


@rem -


@rem look for given ORACLE_SID

@rem -


@if not %1#==# set ORACLE_SID=%1

@rem -


@rem write script v9start.sql to start database

@rem -


echo WHENEVER SQLERROR exit SQL.SQLCODE > v9start.sql

echo connect / as sysdba >> v9start.sql

echo startup >> v9start.sql

echo exit >> v9start.sql

@rem -


@rem execute script v9start.sql

@rem -


@sqlplus /nolog @v9start.sql

JPReyes
Active Contributor
0 Kudos

Check that the environmental variables are set properly...

Its all on the note.

Regards

Juan

markus_doehr2
Active Contributor
0 Kudos

> LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 29-MAY-2009 12:25

Oracle 10.2.0.1 was never supported and has serious bugs. If you read the installation guide attentively you will notice that

- you need to install the latest patchset

- you need to install the latest interim patch

before you start the DB instance installation.

I suggest:

- uninstall the current system + database

- uninstall Oracle

- install Oracle again (10.2.0.1) from the DVD

- use note "Note 839187 - Oracle 10.2.0: Applying patch set/patches/patch collection" to patch the system up according to the installation guide (latest patchset plus interim patch)

- install the database instance

Since parts of the database is loaded already and the version you use contains bugs that may produce corrupt blocks it's the best to start from scratch.

Markus

Former Member
0 Kudos

Hi,

Let us know your database and sitting on which OS.

Rgds

Answers (1)

Answers (1)

Former Member
0 Kudos

Check whether Database is working or not. if it is not then start it manually. check listner status also.

Thanks

presu