| ORA-01078: failure in processing system parameters [message #148072] |
Tue, 22 November 2005 09:35  |
TLegend33
Messages: 203
Registered: March 2005
|
Senior Member |
|
|
I have a client running two 8.1.7 databases on the same Windows 2000 server. Whenever the server is rebooted for maintenance purposes, both windows oracle services start for each database, but only one of the databases will start. The other database does not start and I've only been able to find an error message in the oradim log:
ORA-01078: failure in processing system parameters
From what I've read, the specific parameter should be specified somewhere in a log file, however I'm not sure what log file this would be written to. The alert log does not list the error and the oradim log only gives me the error message. How can I find out which parameter is causing the issue? Is there an additional tracing parameter I can put on the service to determine why the service is starting and the database is not?
Thanks.
|
|
|
|
|
|
| Re: ORA-01078: failure in processing system parameters [message #148099 is a reply to message #148072] |
Tue, 22 November 2005 15:20  |
TLegend33
Messages: 203
Registered: March 2005
|
Senior Member |
|
|
Unfortunately, I could not reproduce the error with the recommended steps. The database started fine when issuing the startup pfile= command. However, the database still will not start when the windows service is started. I'm not sure what you mean when you ask;'Post the post snapshot of your session'. Below is the init.ora I've been working with:
# _system_trig_enabled=false
#
# Copyright (c) 1991, 2000 by Oracle Corporation
###############################################################################
db_name = "DB1"
db_domain = WORLD
instance_name = DB1
service_names = DB1.WORLD
db_files = 1024
control_files = ("c:\oracle\oradata\DB1\control01.ctl"
, "F:\Data\oracle\oradata\DB1\control02.ctl"
, "F:\Data\oracle\oradata\DB1\control03.ctl")
# checkpoint_process = TRUE # cls 03.08.05
compatible = 8.0.5
# db_file_multiblock_read_count = 8
db_file_multiblock_read_count = 12 # cls 03.08.05
# db_block_buffers = 384000 # cls 03.08.05 1.5G
db_block_buffers = 300000 # cls 03.07.16 1.22G
# db_block_buffers = 12800
shared_pool_size = 524288000 # cls 03.07.16 500M
large_pool_size = 52428800 # cls 03.07.16 cls 50 M
java_pool_size = 0
license_max_sessions = 40 # cls 03.07.30 per David Aziz
log_buffer = 1048576 # 03.08.05
log_checkpoint_interval = 1000000 # 03.08.01
log_checkpoint_timeout = 0 # 03.08.01
# log_buffer = 32768
# log_buffer = 65536 # 03.08.01
# log_checkpoint_interval = 10000
# log_checkpoint_timeout = 1800
max_enabled_roles = 30
open_cursors = 300
processes = 150
parallel_max_servers = 5
#audit_trail = true # if you want auditing
#timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5M each
log_archive_start = true
log_archive_dest = F:\data\Archive\DB1
log_archive_format = DB1%S.ARC
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
#rollback_segments = ( RBS0, RBS1, RBS2, RBS3, RBS4, RBS5, RBS6, RBS7, RBS8, RBS9, RBS10, RBS11, RBS12, RBS13, RBS14, RBS15, RBS16, RBS17, RBS18, RBS19, RBS20, RBS21, RBS22, RBS23, RBS24 )
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = true
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = true
oracle_trace_collection_name = ""
# define directories to store trace and alert files
background_dump_dest = c:\oracle\admin\DB1\bdump
#Uncomment this parameter to enable resource management for your database.
#The SYSTEM_PLAN is provided by default with the database.
#Change the plan name if you have created your own resource plan.# resource_manager_plan = system_plan
user_dump_dest = c:\oracle\admin\DB1\udump
db_block_size = 4096
#updated from exclusive (error processing sys params) tc 11/21/2005
remote_login_passwordfile = shared
os_authent_prefix = ""
distributed_transactions = 500
# mts_dispatchers = "(protocol=TCP)"
# mts_dispatchers = "(PROTOCOL=TCP)(DISPATCHERS=3)" # cls 03.07.16
# mts_max_dispatchers = 5 # cls 03.07.16
# mts_servers = 10 # cls 03.07.16
# mts_max_servers = 20 # cls 03.07.16
sort_area_size = 65536
sort_area_retained_size = 65536
|
|
|
|
|
|
| Re: ORA-01078: failure in processing system parameters [message #148321 is a reply to message #148104] |
Wed, 23 November 2005 10:50 |
TLegend33
Messages: 203
Registered: March 2005
|
Senior Member |
|
|
Ah, I see.
I can't re-execute the commands as it's a production system, but I can recreate them below:
set oracle_sid=db1
svrmgrl
connect username/password
shutdown immediate
(At this point, I start the "OracleServiceDB1" from the control panel, which starts up but does not start the database. After this, I maximize my command window with server manager still running)
connect username/password@db1
startup pfile=c:\oracle\ora81\database\initdb1.ora
The database then mounted and opened appropriately without any errors. I can't find anything wrong with the init parameters either.
I did not try these steps with the second instance on the server because that oracle service & the database start up appropriately.
I have not tried recreating the service again with oradim since it's production. I may be able to plan some down time with the client to do just that. I'm not sure that will be the answer though. I would like to see a log of which initialization parameter is causing the error in the oradim.log.
|
|
|
|
| Re: ORA-01078: failure in processing system parameters [message #148322 is a reply to message #148321] |
Wed, 23 November 2005 10:53 |
 |
Mahesh Rajendran
Messages: 10708
Registered: March 2002
Location: oracleDocoVille
|
Senior Member
Account Moderator |
|
|
>>The database then mounted and opened appropriately without any errors. I can't find anything wrong with the init parameters either
Something wrong with your services then. May be it is looking into wrong SID.
Try recreating the service.
I do not have windows machine around or even 8i and cannot simulate it.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
