sapinst error during Oracle Pre-load phase

[Former Member]

Dear experts

I am doing fresh install of  NW 640 SR1 EXT2 (Web AS ABAP only) on Linux x86_64 and Oracle 11.2. Oracle Client is 10.2.0.5 (Thats the combination allowed)

Part of this pre-build went fine and database starts and stops fine and I restarted database with no issues. This happened in the middle.

Getting this error:

sapinst log

ERROR 2012-05-12 07:12:04

CJS-00084  SQL statement or script failed. DIAGNOSIS: Error message: Executable /oraunix/BD1/112_64/bin/sqlplus returns 227.. SOLUTION: For more information, see ora_sql_results.log and the Oracle documentation.

ERROR 2012-05-12 08:00:41

CJS-00084  SQL statement or script failed. DIAGNOSIS: Error message: ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instanceORACLE instance started.

When I look at the logs it does not tell me what exact parameter is obsolete.

In the ora_sql.log file all it says is:

connect  / as sysdba ;

@@"/sapstage/temp/sapinst_instdir/NW04/SYSTEM/ABAP/ORA/UC/DB/oradbusr.sql"

exit;

Executed with error.

In the ora_sql_results.log file it says:

Connected to an idle instance.

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area 3708055552 bytes

Fixed Size                  2231888 bytes

Variable Size            1862271408 bytes

Database Buffers         1828716544 bytes

Redo Buffers               14835712 bytes

ORA-01102: cannot mount database in EXCLUSIVE mode

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SAPINST: End of output of SQL executing program /oraunix/BD1/112_64/bin/sqlplus.

SAPINST found errors.

SAPINST The current process environment may be found in sapinst_ora_environment.log.

2012-05-12, 08:00:41 SAPINST ORACLE stop logging

I Do not see a spfile under dbs but did check the pfile (initBD1.ora) and could not find a bad parameter. Pasted here to see if you find anything unusual:

shared_pool_size = 1817601638

open_cursors = 2000

# processes = ABAP-Workprozesse * 2 + J2EE-Serverprozesse *

# <max-connections> + PARALLEL_MAX_SERVERS + 40

processes = 80

# session = 2 * processes

sessions  = 96

db_name = BD1

db_block_size = 8192

remote_os_authent = true

# retention time for RMAN backup information in control file

control_file_record_keep_time = 30

log_checkpoints_to_alert = true

compatible = 11.2.0

parallel_execution_message_size = 16384

query_rewrite_enabled = false

replication_dependency_tracking = false

star_transformation_enabled = true

log_archive_dest_1 = 'LOCATION=/oracle/BD1/oraarch/BD1arch'

log_archive_format = %t_%s_%r.dbf

undo_tablespace = PSAPUNDO

pga_aggregate_target = 2423468851

db_cache_size = 1817601638

remote_login_passwordfile = exclusive

recyclebin = off

FILESYSTEMIO_OPTIONS = setall

diagnostic_dest = /oracle/BD1/saptrace

audit_file_dest = /oracle/BD1/saptrace/audit

_OPTIM_PEEK_USER_BINDS = FALSE

_OPTIMIZER_MJC_ENABLED = FALSE

_B_TREE_BITMAP_PLANS = FALSE

_INDEX_JOIN_ENABLED = FALSE

_IN_MEMORY_UNDO = FALSE

_SORT_ELIMINATION_COST_RATIO = 10

_TABLE_LOOKUP_PREFETCH_SIZE = 0

db_recovery_file_dest = /oracle/BD1/oraflash

db_recovery_file_dest_size = 30000M

max_dump_file_size = 20000

parallel_threads_per_cpu = 1

deferred_segment_creation = true

control_files = (/oracle/BD1/origlogA/cntrl/cntrlBD1.dbf, /orafiles/BD1/sapdata1/system_1/cntrl/cntrlBD1.dbf, /orac

le/BD1/saparch/cntrl/cntrlBD1.dbf)

Please  help !!

[Former Member]

Hi Bobby,

The issue is not due to obsolete or deprecated parameter(s). The issue is due to the fact that

ORA-01102: cannot mount database in EXCLUSIVE mode.

The oracle cannot be mount in EXCLUSIVE mode may be because some other instance has already mounted the database in exclusive or parallel mode.

I would suggest you to check if the

1. the processes for Oracle (pmon, smon, lgwr and dbwr) still exist.

If background processes exist, remove them by using the Unix command "kill". For example:

kill -9 <Process_ID_Number>

2. shared memory segments and semaphores still exist even though the

database has been shutdown

ipcs -b <ora user>

Please check the Alert logs  in /oracle/<SID>/saptrace/background/.

-Renu

[Former Member]

Hi Renu

Thank you for your reply. You are correct even after shutting down Oracle some of those processes were still there. I killed those and also the shared mem segments. Then also rebooted the whole server. Not much luck. As you can see below the database starts and mounts fine.

ERROR	2012-05-12 15:29:27 [iaxxinscbk.cpp:289]
	abortInstallation

CJS-00084  SQL statement or script failed. DIAGNOSIS: Error message: ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area 3708055552 bytes

Fixed Size	2231888 bytes
Variable Size	1862271408 bytes
Database Buffers	1828716544 bytes
Redo Buffers	14835712 bytes

Database mounted.

Database opened.

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

. SOLUTION: For more information, see ora_sql_results.log and the Oracle documentation.

The logs show the same message as above. Also I dont see a alert log file and thats possibly because the parameter background_dump_dest is not created yet may be >

[former_member189725]

Hi ,

The issue is not with deprecated parameters , is it because of some other reason . Please try to give full permission to the installation directory and retry.In  Oracle 11g the  parameter remote_os_authent = true is considered deprecated , hence the error . But the SAP system cannot function without this parameter as it uses the OPS$ mechanism . Hence you will get this error even on an operational 11g system.

Regards

Ratnajit

[Former Member]

I did search on SDN prior to posting and this obsolete parameter issue has already been discussed many times. That is not our issue here. We are aware that its only a warning. Our issue is sapinst being stuck at the pre-load stage. And yes basic things such as rebooting the server, giving full permission to all related directories etc are done without success.

[former_member197466]

Hi Bobby,

Can you please copy paste the latest error in ora_sql_results.log here?

Please double check SAP note 439637 for the possible reasons of ORA-01102.

Cheers,

Ivy