-
oracle startup problem on IBM AIX server
I am not able to do the normal startup of oracle 10g in IBM AIX server I posting the error log.
Need help in resolving this problem
Mon Jul 5 17:02:11 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =121
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 1000
sga_max_size = 3221225472
shared_pool_size = 838860800
java_pool_size = 117440512
nls_language = AMERICAN
control_files = /data1/oracledb/oradata/control/control01.ctl, /data1/oracledb/isddb/control/control02.ctl
db_block_size = 8192
db_cache_size = 1291845632
db_keep_cache_size = 268435456
compatible = 10.2.0.1.0
log_archive_dest_1 = LOCATION=/data4/isddb/archive
log_archive_dest_2 = LOCATION=/data5/isddb/archive
log_archive_dest_state_1 = ENABLE
log_archive_max_processes= 5
log_archive_format = arch_%r_%t_%s.arc
log_buffer = 14302720
fast_start_mttr_target = 0
undo_management = AUTO
undo_tablespace = undotbs1
undo_retention = 3000
O7_DICTIONARY_ACCESSIBILITY= FALSE
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = ISDDB
service_names = ISDDB
session_cached_cursors = 100
job_queue_processes = 10
cursor_sharing = similar
background_dump_dest = /data1/oracledb/app/dumps/bdump
user_dump_dest = /data1/oracledb/app/dumps/udump
core_dump_dest = /data1/oracledb/app/dumps/cdump
audit_trail = TRUE
db_name = ISDDB
open_cursors = 300
os_authent_prefix =
optimizer_mode = choose
pga_aggregate_target = 629145600
workarea_size_policy = auto
PMON started with pid=2, OS id=368824
PSP0 started with pid=3, OS id=549308
MMAN started with pid=4, OS id=237724
DBW0 started with pid=5, OS id=1810524
LGWR started with pid=6, OS id=360824
CKPT started with pid=7, OS id=1806348
SMON started with pid=8, OS id=340460
RECO started with pid=9, OS id=311604
CJQ0 started with pid=10, OS id=450792
MMON started with pid=11, OS id=553326
MMNL started with pid=12, OS id=541124
Mon Jul 5 17:02:11 2010
Oracle Data Guard is not available in this edition of Oracle.
Mon Jul 5 17:02:11 2010
ALTER DATABASE MOUNT
Mon Jul 5 17:02:15 2010
Setting recovery target incarnation to 1
Mon Jul 5 17:02:15 2010
Successful mount of redo thread 1, with mount id 1796698643
Mon Jul 5 17:02:15 2010
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Mon Jul 5 17:02:16 2010
ALTER DATABASE OPEN
Mon Jul 5 17:02:16 2010
Beginning crash recovery of 1 threads
Mon Jul 5 17:02:16 2010
Started redo scan
Mon Jul 5 17:02:16 2010
Completed redo scan
1 redo blocks read, 0 data blocks need recovery
Mon Jul 5 17:02:16 2010
Started redo application at
Thread 1: logseq 26, block 2, scn 564335
Mon Jul 5 17:02:16 2010
Recovery of Online Redo Log: Thread 1 Group 2 Seq 26 Reading mem 0
Mem# 0 errs 0: /data1/oracledb/oradata/redo/redo02.log
Mon Jul 5 17:02:16 2010
Completed redo application
Mon Jul 5 17:02:16 2010
Completed crash recovery at
Thread 1: logseq 26, block 3, scn 584337
0 data blocks read, 0 data blocks written, 1 redo blocks read
Mon Jul 5 17:02:16 2010
Thread 1 advanced to log sequence 27
Thread 1 opened at log sequence 27
Current log# 3 seq# 27 mem# 0: /data1/oracledb/oradata/redo/redo03.log
Successful open of redo thread 1
Mon Jul 5 17:02:16 2010
SMON: enabling cache recovery
Mon Jul 5 17:02:16 2010
Errors in file /data1/oracledb/app/dumps/udump/isddb_ora_389510.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Mon Jul 5 17:02:16 2010
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 389510
ORA-1092 signalled during: ALTER DATABASE OPEN...
-
Which version was the 10.2.0.1 database before, and what were you doing in terms of upgrading to 10.2.0.1?
-
Agreed.
It looks like an incomplete upgrade scenario, this is consistent with having upgraded Oracle codeset but not having upgraded Oracle instance. Each individual instance has to be upgraded after upgrading Oracle codeset.
If this is the case double-check Oracle upgrade README file for proper procedure.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
-
I have installed Oracle10G for the first time on IBM's AIX server
i have created database manually.
i got following error in
startup.log:
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jul 6 12:17:17 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> Connected to an idle instance.
SQL> ORACLE instance started.
Total System Global Area 3221225472 bytes
Fixed Size 2024344 bytes
Variable Size 1644170344 bytes
Database Buffers 1560281088 bytes
Redo Buffers 14749696 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
and in alert.log file contains following error
ARCH: Archival disabled due to shutdown: 1090
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1090
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Tue Jul 6 12:09:33 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =121
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 1000
sga_max_size = 3221225472
shared_pool_size = 838860800
java_pool_size = 117440512
nls_language = AMERICAN
control_files = /data1/oracledb/oradata/control/control01.ctl, /data1/oracledb/isddb/control/control02.ctl
db_block_size = 8192
db_cache_size = 1291845632
db_keep_cache_size = 268435456
compatible = 10.2.0.1.0
log_archive_dest_1 = LOCATION=/data4/isddb/archive
log_archive_dest_2 = LOCATION=/data5/isddb/archive
log_archive_dest_state_1 = ENABLE
log_archive_max_processes= 5
log_archive_format = arch_%r_%t_%s.arc
log_buffer = 14302720
fast_start_mttr_target = 0
undo_management = AUTO
undo_tablespace = undotbs1
undo_retention = 3000
O7_DICTIONARY_ACCESSIBILITY= FALSE
remote_login_passwordfile= EXCLUSIVE
db_domain =
instance_name = ISDDB
service_names = ISDDB
session_cached_cursors = 100
job_queue_processes = 10
cursor_sharing = similar
background_dump_dest = /data1/oracledb/app/dumps/bdump
user_dump_dest = /data1/oracledb/app/dumps/udump
core_dump_dest = /data1/oracledb/app/dumps/cdump
audit_trail = TRUE
db_name = ISDDB
open_cursors = 300
os_authent_prefix =
optimizer_mode = choose
pga_aggregate_target = 629145600
workarea_size_policy = auto
PMON started with pid=2, OS id=471292
PSP0 started with pid=3, OS id=237736
MMAN started with pid=4, OS id=368654
DBW0 started with pid=5, OS id=450680
LGWR started with pid=6, OS id=1806486
CKPT started with pid=7, OS id=573706
SMON started with pid=8, OS id=569774
RECO started with pid=9, OS id=282714
CJQ0 started with pid=10, OS id=311434
MMON started with pid=11, OS id=1798252
MMNL started with pid=12, OS id=458882
Tue Jul 6 12:09:34 2010
Oracle Data Guard is not available in this edition of Oracle.
Tue Jul 6 12:09:46 2010
alter database mount
Tue Jul 6 12:09:50 2010
Setting recovery target incarnation to 1
Tue Jul 6 12:09:50 2010
Successful mount of redo thread 1, with mount id 1796750602
Tue Jul 6 12:09:50 2010
Database mounted in Exclusive Mode
Completed: alter database mount
Tue Jul 6 12:09:59 2010
alter database open
Tue Jul 6 12:09:59 2010
Beginning crash recovery of 1 threads
Tue Jul 6 12:09:59 2010
Started redo scan
Tue Jul 6 12:09:59 2010
Completed redo scan
1 redo blocks read, 0 data blocks need recovery
Tue Jul 6 12:09:59 2010
Started redo application at
Thread 1: logseq 28, block 2, scn 604343
Tue Jul 6 12:09:59 2010
Recovery of Online Redo Log: Thread 1 Group 1 Seq 28 Reading mem 0
Mem# 0 errs 0: /data1/oracledb/oradata/redo/redo01.log
Tue Jul 6 12:09:59 2010
Completed redo application
Tue Jul 6 12:09:59 2010
Completed crash recovery at
Thread 1: logseq 28, block 3, scn 624345
0 data blocks read, 0 data blocks written, 1 redo blocks read
Tue Jul 6 12:10:00 2010
Thread 1 advanced to log sequence 29
Thread 1 opened at log sequence 29
Current log# 2 seq# 29 mem# 0: /data1/oracledb/oradata/redo/redo02.log
Successful open of redo thread 1
Tue Jul 6 12:10:00 2010
SMON: enabling cache recovery
Tue Jul 6 12:10:00 2010
Errors in file /data1/oracledb/app/dumps/udump/isddb_ora_242034.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Tue Jul 6 12:10:00 2010
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 242034
ORA-1092 signalled during: alter database open...
-
the error is quite clear - what dont you understand about it?
do you actually have a database?
-
I did install the Oracle10g
and it showed successful installation but we have not done optional configuration settings.
Later we executed netca and
later we created the database but without creating the system01.dbf file.
and it was done successfully
I forgot to create the dbstart and pwd file previously so
I created the dbstart and pwd file but after creation of the database.
is it necessary to provide it with the system01.dbf file also?
Last edited by aryaanu; 07-06-2010 at 04:35 AM.
-
how did you created the database with out mandatory system table space? It seems you messed up. Better clean-up, read some oracle documentation then create the database again.
Thanks,
Vijay Tummala
Try hard to get what you like OR you will be forced to like what you get.
-
Originally Posted by aryaanu
...later we created the database but without creating the system01.dbf file.
and it was done successfully
Hard to believe - Check log harder.
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
-
Try these steps
Create a Database Manually
Step 1: Decide on Your Instance's System Identifier (SID) The first step in creating the database is to determine the System Identifier (SID).
This is what the environment will be set to when your database starts up
and shuts down, and what the instance processes will have in their names as unique identifiers.
My Instance name is called cat1020 you can use whatever you want. So
wherever you see cat1020 replace with your name. Of course, use file system
paths that are relavant to your machine.
export ORACLE_SID=cat1020
Step 2: Create the Initialization Parameter File (sample file below)
$ cat $ORACLE_HOME/dbs/initcat1020.ora
*.db_name='cat1020'
*.DB_UNIQUE_NAME='cat1020'
*.instance_name='cat1020'
*.background_dump_dest='/rdbms/oracle_data/10.2.0/cat/bdump'
*.compatible='10.2.0.1.0'
*.control_files='/rdbms/oracle_data/10.2.0/cat/control01.ctl','/rdbms/oracle_dat
a/10.2.0/cat/control02.ctl','/rdbms/oracle_data/10.2.0/cat/control03.ctl'
*.core_dump_dest='/rdbms/oracle_data/10.2.0/cat/cdump'
*.db_block_size=4096
*.db_cache_size=30m
*.db_domain='world.com'
*.java_pool_size=31457280
*.job_queue_processes=20
*.large_pool_size= 8388608
*.log_archive_dest='/rdbms/oracle_data/10.2.0/cat/arch'
*.log_archive_format='arch%s%r%t.arc'
*.max_dump_file_size='10000'
*.nls_sort='binary'
*.open_cursors=300
*.pga_aggregate_target=100m
*.processes=300
*.remote_login_passwordfile='EXCLUSIVE'
*.service_names='cat1020'
*.sga_max_size=400m
*.shared_pool_size=153431142
*.undo_management='AUTO'
*.undo_retention=10800
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='/rdbms/oracle_data/10.2.0/cat/udump'
*.workarea_size_policy='auto
Step 3: Connect to and Start the Instance
Connect to the instance as SYSDBA either using operating system authentication or the password file method of authentication and start up the instance using the STARTUP command.
>sqlplus '/ as sysdba'
NOTE: If your parameter file is not in the default location or is not named init.ora, you may need to specify the PFILE clause in the STARTUP command for the instance to start. Because you do not yet have a database attached to the instance, you need to start up the instance in NOMOUNT state:
SQL> startup nomount; The instance is now started and ready for the CREATE DATABASE command.
#
# Change the numbers as you see fit for your environment.
#
Step 4: Issue the CREATE DATABASE Statement
create database cat1020
user sys identified by sys
user system identified by system
logfile group 1 ('/rdbms/oracle_data/10.2.0/cat/redo01.log') size 5M,
group 2 ('/rdbms/oracle_data/10.2.0/cat/redo02.log') size 5M,
group 3 ('/rdbms/oracle_data/10.2.0/cat/redo03.log') size 5M
MAXLOGFILES 5
MAXLOGMEMBERS 5
MAXLOGHISTORY 1
MAXDATAFILES 100
MAXINSTANCES 1
CHARACTER SET US7ASCII
NATIONAL CHARACTER SET AL16UTF16
datafile '/rdbms/oracle_data/10.2.0/cat/system01.dbf' size 400M
extent management local
default temporary tablespace temp
tempfile '/rdbms/oracle_data/10.2.0/cat/temp.dbf' size 25M
undo tablespace undotbs1
datafile '/rdbms/oracle_data/10.2.0/cat/undotbs.dbf'
size 25M reuse autoextend on next 1M maxsize unlimited
sysaux DATAFILE '/rdbms/oracle_data/10.2.0/cat/sysaux01.dbf' SIZE 500M;
Step 5: Run Scripts to Build Data Dictionary Views
@$ORACLE_HOME/rdbms/admin/catalog.sql
@$ORACLE_HOME/rdbms/admin/catproc.sql
REM * Alter SYS and SYSTEM users.
REM *
alter user sys identified by sys temporary tablespace temp;
alter user system identified by system temporary tablespace temp;
REM * For each DBA user, run DBA synonyms SQL script. Don't forget that EACH
REM * DBA USER created in the future needs dba_syn.sql run from its account.
REM *
connect system/manager
@$ORACLE_HOME/rdbms/admin/catdbsyn.sql
@$ORACLE_HOME/sqlplus/admin/pupbld.sql
Step 6: Create a Server Parameter File
This step is optional, although highly recommended by Oracle. Your Oracle database was created by starting the instance with a parameter file, or PFILE. Because it is editable, you can migrate, easily, your new database to using a server parameter file. Creation of the server parameter file (or spfile) is accomplished by issuing the following statement:
Create spfile from pfile;
Good luck
-
Thanks
Thank you BeefStu
your instructions was really helpful I am successfully able to create database and able to connect database.
Previously my only problem was that I forgot to create the sys files
Thank you
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|