| Creating a database manually [message #64021] |
Tue, 07 December 2004 00:33  |
Rod
Messages: 3
Registered: November 2000
|
Junior Member |
|
|
Hello,
I am new to Oracle and have been going through the process of creating a db and have done the following:
1. created an initialisation file
2. did the ORADIM thing
3. set ORACLE_SID
4. connect as SYSDBA
5. start the instance pointing to the pfile
Up to here everything was going smoothly. However when I try to create a Database using the script:
CREATE DATABASE TRYONE
CONTROLFILE REUSE
LOGFILE 'C:Oracle8ioradataTRYONEredo01.log' SIZE 1M REUSE,
'c:Oracle8ioradataTRYONEredo02.log' SIZE 1M REUSE,
'c:Oracle8ioradataTRYONEredo03.log' SIZE 1M REUSE,
.......
i get the following errors:
SP2-0734: unknown command beginning "CONTROLFIL..." - rest of line ignored.
SP2-0734: unknown command beginning "LOGFILE '..." - rest of line ignored.
SP2-0734: unknown command beginning "'c:Oracle..." - rest of line ignored.
SP2-0734: unknown command beginning "'c:Oracle..." - rest of line ignored.
SP2-0734: unknown command beginning "'c:Oracle..." - rest of line ignored.
Any help with resolving this will be greatly appreciated.
Thanks
|
|
|
|
|
|
| Re: Creating a database manually [message #64025 is a reply to message #64021] |
Tue, 07 December 2004 01:57  |
Nino
Messages: 6
Registered: November 2004
|
Junior Member |
|
|
Hi,
sqlplus complained each line except the first. This behavior happens when you separate each line with the semicolon so sqlplus recognizes them each line as a command, but apparently you didn't.
The server should additionally complain about the first line because of the 'incomplete command'.
Possibly the command or line separator setting is changed in your login.sql.
Could you post how you issued the command and how you terminated it in the script?
cheers
|
|
|
|
| Re: Creating a database manually : sp2 - 0734 [message #64591 is a reply to message #64021] |
Fri, 11 February 2005 03:23 |
rajesh
Messages: 173
Registered: November 1998
|
Senior Member |
|
|
Couple of things
i. check the sql client version. if it is of a lower version it may not work. it could be a sql client problem
ii. At times, it could be a problem of stty erase value in a unix system, and when typing the command, if you had wrongly used backspace key for deleting characters in the command, the query/sql command is NOT actually typed correctly. In this case, try the query/command again.. it has worked for me a few times
iii. put the sqls in a script and execute the script and will mostly work
alright three things
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
