Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Sapinst error during DB creation

Hello,

I am installing a SolMan 7.1 with Oracle 11.2.0.3.5.

During the DB creation sapinst stop with the following error:

---

An error occurred while processing option SAP Solution Manager 7.1 Support Release 1 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step: SQL statement or script failed. DIAGNOSIS: Error message: ORA-01078: failure in processing system parameters ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance Disconnected . SOLUTION: For more information, see ora_sql_results.log and the Oracle documentation.). You can now:

Choose Retry to repeat the current step.

Choose Log Files to get more information about the error.

Stop the option and continue with it later.

Log files are written to /var/tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS.

---

The error is because of an invalid parameter:

---

================================================================================

2013-03-05, 15:05:38 SAPINST ORACLE start logging for

STARTUP NOMOUNT;

exit;

Output of SQL executing program:

SQL*Plus: Release 11.2.0.3.0 Production on Tue Mar 5 15:05:38 2013

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Connected to an idle instance.

ORA-01078: failure in processing system parameters

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

Disconnected

SAPINST: End of output of SQL executing program /oracle/SSM/112_64/bin/sqlplus.

SAPINST found errors.

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

2013-03-05, 15:05:38 SAPINST ORACLE stop logging

---

I would like to know which parameter is causing the problem.

But No alert log is created.

How can I get the name of the invalid parameter?

Here is the Oracle profile generated by sapinst:

---

cat initSSM.ora

###########################################################

#  (c)Copyright SAP AG, Walldorf                          #

# @(#) $Id: //bas/720_REL/src/krn/tpls/ora/INITSIDBASE.ORA#5 $

###########################################################

shared_pool_size = 1132462080

open_cursors = 2000

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

# <max-connections> + PARALLEL_MAX_SERVERS + 40

processes = 1070

# session = 2 * processes

sessions = 2140

db_name = SSM

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/SSM/oraarch/SSMarch'

log_archive_format = %t_%s_%r.dbf

undo_tablespace = PSAPUNDO

pga_aggregate_target = 1509949440

db_cache_size = 1132462080

remote_login_passwordfile = exclusive

recyclebin = off

FILESYSTEMIO_OPTIONS = setall

diagnostic_dest = /oracle/SSM/saptrace

audit_file_dest = /oracle/SSM/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/SSM/oraflash

db_recovery_file_dest_size = 30000M

max_dump_file_size = 20000

parallel_threads_per_cpu = 1

control_files = (/oracle/SSM/origlogA/cntrl/cntrlSSM.dbf, /oracle/SSM/origlogB/cntrl/cntrlSSM.dbf, /oracle/SSM/sapdata1/cntrl/cntrlSSM.dbf)

---

Former Member replied

Hi,

I feel the following parameter might be the issue.

log_archive_dest_1 = 'LOCATION=/oracle/SSM/oraarch/SSMarch'

Please replace the above parmeter with the below one and see  whether it helps.

log_archive_dest_1 = 'LOCATION=/oracle/SSM/oraarch/SSMarch'

Thanks and Regards,

Vimal

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question