Databases
cancel
Showing results for 
Search instead for 
Did you mean: 

Getting error creating database

SOLVED
Go to solution
Emil Velez
Honored Contributor

Getting error creating database

I am using the following commands to create the database and getting a error.

Points will be provided

$ mkdir /opt/oracle/oradata
$ mkdir /opt/oracle/oradata/ver11
$ /opt/oracle/product/11.1.0.db/bin/sqlplus / as sysdba

SQL*Plus: Release 11.1.0.6.0 - Production on Tue Jun 8 16:52:48 2010

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

Connected to an idle instance.

SQL> connect SYS/hp as SYSDBA
CREATE SPFILE='/opt/oracle/product/11.1.0.db/dbs/spfilever11.ora' FROM
PFILE='/tmp/oracle/inittemplate.ora';
SHUTDOWN
Connected to an idle instance.
SQL> 2
File created.

SQL> ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
HPUX-ia64 Error: 2: No such file or directory
SQL> startup nomount
ORACLE instance started.

Total System Global Area 521936896 bytes
Fixed Size 2108344 bytes
Variable Size 171967560 bytes
Database Buffers 343932928 bytes
Redo Buffers 3928064 bytes
SQL> CREATE DATABASE ver11
2 USER SYS IDENTIFIED BY hp
3 USER SYSTEM IDENTIFIED BY hp
4 LOGFILE GROUP 1 ('/opt/oracle/oradata/ver11/redo01.log') SIZE 100M,
5 GROUP 2 ('/opt/oracle/oradata/ver11/redo02.log') SIZE 100M,
6 GROUP 3 ('/opt/oracle/oradata/ver11/redo03.log') SIZE 100M
7 MAXLOGFILES 5
8 MAXLOGMEMBERS 5
9 MAXLOGHISTORY 1
10 MAXDATAFILES 100
11 MAXINSTANCES 1
12 CHARACTER SET US7ASCII
13 NATIONAL CHARACTER SET AL16UTF16
14 DATAFILE '/opt/oracle/oradata/ver11/system01.dbf' SIZE 325M REUSE
15 EXTENT MANAGEMENT LOCAL
16 SYSAUX DATAFILE '/opt/oracle/oradata/ver11/sysaux01.dbf' SIZE 325M REUSE
17 DEFAULT TABLESPACE tbs_1
18 DEFAULT TEMPORARY TABLESPACE tempts1
19 TEMPFILE '/opt/oracle/oradata/ver11/temp01.dbf'
20 SIZE 20M REUSE
21 UNDO TABLESPACE undotbs
22 DATAFILE '/opt/oracle/oradata/ver11/undotbs01.dbf'
23 SIZE 200M REUSE AUTOEXTEND ON MAXSIZE UNLIMITED;
CREATE DATABASE ver11
*
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
Process ID: 4706
Session ID: 1200 Serial number: 5



As you can see oracle dies..

Any help will be appreciated.

Just trying to create a simple instance from a script
12 REPLIES
Emil Velez
Honored Contributor

Re: Getting error creating database

This is oracle 11.1.0 on HPUX 11.31

with the DCOE OE
Sameer_Nirmal
Honored Contributor

Re: Getting error creating database

You may want to check alert log to know the reason why Oracle is being terminated.
TwoProc
Honored Contributor

Re: Getting error creating database

I think it might be that you're creating log groups, when you just need logfiles. Groups are for when you want multiple destinations, and you don't have them.

Just trying leaving the "LOGGROUP N (xxxx)"
directives out and re-running.

Reason: I believe I tried this years ago (groups of one), and got the same result, but in an older version of the database (9i).

We are the people our parents warned us about --Jimmy Buffett
RobertBlok
Occasional Advisor

Re: Getting error creating database

Check the existance of all the directories (adump, bdump, cdump etc).

SQL> show parameter dump

Cheers,
Robert.
Jean-Luc Oudart
Honored Contributor

Re: Getting error creating database

Hi

just a simple question. Have you checked your oracle environment variables (ORACLE_HOME, ORACLE_SID, ...).
Any dump file provided ?

Have you tried to create the database with dbca ?

Regards
Jean-Luc
fiat lux
Aneesh Mohan
Honored Contributor

Re: Getting error creating database

Hi,

The reason should available in the alert log.

Also ..
Check the syntax in line 17 ..it appear to me like you are missing datafile over there.


Aneesh
TwoProc
Honored Contributor

Re: Getting error creating database

For the phrase "autoextend on" isn't there something like a "next 4m" (example size) that's required on that? I don't think it allows for an undefined autoextend, and - even if it does allow for it syntactically, man - it's going to be small, resulting in really cut up and chained data files, they all of the file autoextend and grow.
We are the people our parents warned us about --Jimmy Buffett
Volker Borowski
Honored Contributor
Solution

Re: Getting error creating database

Hi,

check your init.ora for
parameter UNDO_TABLESPACE.
If it does not match exactly to

21 UNDO TABLESPACE undotbs

CREATE DATABASE will fail.

Assuming possible
undotbs vs. undotbs1
missmatch.



Second point:

17 DEFAULT TABLESPACE tbs_1

without tablespace tbs_1 beeing created...???

Delete the line and do
alter database ...
after creating the tablespace later


Hope this helps
Volker

Emil Velez
Honored Contributor

Re: Getting error creating database

Thanks

The inonsistency between the temp tablespace in the init file was the problem.

Now I cannot seem to start the database normaly without getting a error. WHen looking at the alert file it said to use the upgrade option. so I did and it worked.

I always have to open up the database with

startup nomount
alter database open upgrade

any way to startup the database normally without getting a error.

Thanks for any assistance. Unfortunately I am not a card carrying DBA. This is for some testing we are doing on systems.
TwoProc
Honored Contributor

Re: Getting error creating database

Man - if you're having to run that "upgrade" option - I think you need to look in $ORACLE_HOME/rdbms/sql for the cat* script relevant to the database level that you're creating.

Unfortable feeling: I've NEVER had to use the "upgrade" parameter you're describing.
We are the people our parents warned us about --Jimmy Buffett
TwoProc
Honored Contributor

Re: Getting error creating database

also - a reminder - check your autoexend. Since it's not holding you, it means it's taking default value, which may be very, very small (1k perhaps). You really don't want to leave it like that. Your db files will be very cut up over your file system.
We are the people our parents warned us about --Jimmy Buffett
Emil Velez
Honored Contributor

Re: Getting error creating database

the final issue was that the catalog.sql and catproc.sql scripts did not run.