Friday, January 27, 2006

Creating an Oracle (XE) database manually on XP

There are two ways for creating an Oracle database, one is using Oracle Database Configuration Assistant and the other is manually, I'll provide a small step by step guide for the latter on windows XP.

This are the main steps:

1. Create the directory structure
2. Declare an oracle SID name.
3. Create a windows service and password file
4. Create the init.ora file
5. Start the instance in nomount mode
6. Use the Create database command
7. Create Data Dictionary


1. Create the directory structure

Under the admin
directory (C:\oraclexe\app\oracle\admin\) we have to create the structure for the new database (this is called OFA Oracle Flexible Arquitecture), the directory is called oraXE which will be the name of the database, and the directories adump, bdump, cdump, dpdump, pfile, udump are created in it:


2. Declare an oracle SID name.

Using the this command we declare the variable for oracle SID. Since could be more than one oracle instance running, oracle uses the SID to difference them.

set ORACLE_SID=oraXE


3. Create a windows service and password file

Every instance on windows requires a windows service which can be created using oradim tool, the created service can be checked in the services list: type services.msc in the console or a link can be found in the control panel -> admin tools -> Services. Also a password file is created under database directory (ORACLE_HOME\database) with the SID embedded in the name (PWDoraXE.ora), this password file is used to authenticate the DBA before starting an instance.


oradim -new -sid %ORACLE_SID% -intpwd passwordhere -startmode M





Important : Remember to stop the default service for the "XE" database which is called "OracleServiceXE" and start the service just created "OracleServiceoraXE" for our new database in the services console.

4. Create the init.ora file
Open a text editor, add the lines below and save it as
initoraXE.ora in C:\oraclexe\app\oracle\admin\oraXE\pfile\. This are just some basic initial parameters, the ones that are not specified are taken by default.



control_files = (C:\oraclexe\oradata\oraXE\control01.ctl,
C:\oraclexe\oradata\oraXE\control02.ctl,
C:\oraclexe\oradata\oraXE\control03.ctl)
undo_management = auto
db_name = oraXE
db_block_size = 8192


control_files : Here we define where will be our control files, those are used for store management information of the database like location of the datafiles, timestamp of the creation of the database,etc. In this case there are three files copies, its recommended to store each copy on different physical disk which is called multiplexing.

undo_management: this parameter is used for choosing between automatic undo management (AUTO) or manually undo management (MANUAL, this is the default) in the latter is needed to create , size and monitor closely undo (rollback) segments, it's recommended to be set to AUTO.

db_name : The database name must be the same used in the create statement.

db_block_size : The default or standard database block size, this is the mininal logical unit of storage in oracle this should be a multiple of the operating system block size.




5. Start the instance in nomount mode

Before you try to connect to start the instance check that you have the right ORACLE_SID:


echo %ORACLE_SID%
oraXE



You can now authenticate through the operating system (no login or password) to start up the database, like this:


sqlplus /nolog

sql>connect / as sysdba

sql>startup nomount pfile=C:\oraclexe\app\oracle\admin\oraXE\pfile\initoraXE.ora

ORACLE instance started.

Total System Global Area 113246208 bytes
Fixed Size 1246556 bytes
Variable Size 58722980 bytes
Database Buffers 50331648 bytes
Redo Buffers 2945024 bytes

sqlplus /nolog : start the sqlplus client , the "/nolog" is to not be prompted for username/password.

connect / as sysdba : authenticate through the operating system with sysdba privileges. If you don't have the right ORACLE_SID ("oraXE") you may get an "ORA-12560: TNS:protocol adapter error".

startup nomount... : we must startup the db in nomount mode because at this point there a no database (physical files) to mount. The pfile that created in step 4 (C:\oraclexe\app\oracle\admin\oraXE\pfile\initoraXE.ora) must be specified otherwise it will look for the default location. If you get a ORA-01081 error is because probably the "XE" database is already started and you can't have two databases mounted at the same time, so first shutdown the running database using the shutdown command.


6. Use the Create database command

With this command we create the database:


sql> create database oraXE
logfile group 1 ('C:\oraclexe\oradata\oraXE\redo1.log') size 10M,
group 2 ('C:\oraclexe\oradata\oraXE\redo2.log') size 10M,
group 3 ('C:\oraclexe\oradata\oraXE\redo3.log') size 10M
character set WE8ISO8859P1
national character set utf8
datafile 'C:\oraclexe\oradata\oraXE\system.dbf'
size 50M
autoextend on
next 10M maxsize unlimited
extent management local
sysaux datafile 'C:\oraclexe\oradata\oraXE\sysaux.dbf'
size 10M
autoextend on
next 10M
maxsize unlimited
undo tablespace undo
datafile 'C:\oraclexe\oradata\oraXE\undo.dbf'
size 10M
autoextend on
default temporary tablespace temp
tempfile 'C:\oraclexe\oradata\oraXE\temp.dbf'
size 10M
autoextend on;

Database created.



7. Create Data Dictionary

Finally, the scripts for creating the data dictionary are under ORACLE_HOME\rdbms\admin.

Run:

sql> @?\rdbms\admin\catalog.sql
sql> @?\rdbms\admin\catproc.sql


? this will be replaced by the value of $ORACLE_HOME
catalog.sql creates the data dictionary views.
catproc.sql creates the dictionary items necessary for PL/SQL functionality.

47 comments:

Anonymous said...

Hi,

thank you for this article that has made complicated things simple for me. However, to make DB creation possible, it's necessary to allow all tablespaces to grow: the temp tablespace grows to 14 MB during the execution of catproc.sql on Oracle XE 10.2.0.1.0. The undo tablespace would or would not extend later, depending on application. So the last part of the 'create database' command should be changed to something like this:

undo tablespace undo
datafile 'C:\oraclexe\oradata\oraXE\undo.dbf'
size 10M
autoextend on
next 5M maxsize 100M
default temporary tablespace temp
tempfile 'C:\oraclexe\oradata\oraXE\temp.dbf'
size 10M
autoextend on
next 5M maxsize 100M;


Mirko Sebart

carlos mafla said...

Hi Mirko

You're right , actually i forgot to mention that this database was not
intended to be used by any real application just for testing purposes, so the values in the sizes
are aleatory and very small to not use many hard disk space, when i wrote the post i didn't run
the dictionary scripts (you got me :P). The 10M of temporary tablespace would be out of space with practically
any sort without the autoextent on clause as you mention. I'm gonna make the corrections.

Thanks

carlos mafla said...

After recreating the database without 'autoextend on' on the temporary tablespace and running catproc.sql the mentioned error is raised:


BEGIN
*
ERROR at line 1:
ORA-01652: unable to extend temp segment by 256 in tablespace TEMP
ORA-06512: at "SYS.DBMS_STATS", line 13210
ORA-06512: at "SYS.DBMS_STATS", line 13517
ORA-06512: at "SYS.DBMS_STATS", line 15859
ORA-06512: at "SYS.DBMS_STATS", line 15901
ORA-06512: at line 1
ORA-06512: at "SYS.DBMS_REGISTRY", line 585
ORA-06512: at "SYS.DBMS_REGISTRY", line 664
ORA-06512: at line 4

This error si solved adding the 'autoextend on' to the temporary tablespace (at least when
running the script).

Also maybe someone else experience this other problem:


I got a lot of ORA-00604 and ORA-04031 while running catalog.sql :

ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared
pool","select inst_id, plw...","Typecheck","seg:kggfaAllocSeg")


Seems like by default oracle allocates 32M of shared_pool_size:


SQL> show parameters shared%

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
hi_shared_memory_address integer 0
max_shared_servers integer
shared_memory_address integer 0
shared_pool_reserved_size big integer 1677721
shared_pool_size big integer 32M
shared_server_sessions integer
shared_servers integer 0


and its not enough to load the whole script. I increased the value to 64M in the initialization parameters and the scripts then ran without any error.

Anonymous said...

Hello,

it's strange but my DB seems to behave in a different way. I actually *reduced* the SGA and PGA sizes right after the installation through the web interface because I wasn't happy with the huge amount of RAM consumed by Oracle on my 256MB machine. So, SGA target can safely go down from 140MB to 80MB. Reducing it further to 72MB provokes the same error as you mentioned, and 60MB crashes the database so thoroughly that it won't even execute "startup nomount" again. The PGA aggregate target can go down from 16MB to 10MB.

Parts of the SGA, including shared pool, are managed automatically by default; if you set their sizes, you actualy set minimum sizes. In my case, Oracle reserved 48MB (out of 80MB SGA) for the shared pool.
It's too bad that no useful DBA documentation is provided with the XE and one needs to read the "real" 10g documentation, hoping that details we're discussing here work the same way on XE.

Mirko Sebart

Anonymous said...
This comment has been removed by a blog administrator.
Anonymous said...

Super color scheme, I like it! Keep up the good work. Thanks for sharing this wonderful site with us.
»

Anonymous said...
This comment has been removed by a blog administrator.
Anonymous said...
This comment has been removed by a blog administrator.
John said...

Thanks for this solutions. I created my new database on Oracle XE, but now I have problem with connected to it. Start listener service and my new DB service, but I alwey connect to XE database... How can I connect to my new database (from sqlplus and web)?

carlos mafla said...

Hi john,
You may have not defined the SID environment variable or/and you have the XE service started. First, check the actual value of your SID:
c:>echo %ORACLE_XE%,
It should print the name you set, i.e. "OraXE", but not "XE".
Additionally, check your list of services to make sure that you only have one service running which is the one that you created, not the Service to connect to the "XE" db wich is started by default and should be stopped to connect to another db. It can create conflicts when you have more than one process listening.
I hope it helps, bye.

Anonymous said...

please tell me which username / password must I use to connect ot the newly created database

carlos mafla said...

You can connect authenticating with the operating system user:

In a dos window type:

c:> sqlplus /nolog

That will open sqlplus and when you are in sqlplus type:

SQL> connect / as sysdba

If the db is no started type :
startup pfile=C:\oraclexe\app\oracle\admin\oraXE\pfile\initoraXE.ora

Anonymous said...

after the step:
"connect /as sysdba"
i got error:
ORA-12560: TNS:protocol adapter error
i don't know why ;(((
please help ;)

carlos mafla said...

First check that your ORACLE_SID is correct. For example, if you want to connect to a database named "oraXE" you should set your ORACLE_SID to "oraXE":

c:\>set ORACLE_SID=oraXE

Otherwise, you will get:

SQL> connect / as sysdba
ERROR:
ORA-12560: TNS:error del adaptador de protocolo

Also check that the service for the database is running, remember it must be the service for the database name that you have in the ORACLE_SID .
Hope it helps...

mnemotronic AT-SIGN netscape.net said...

Thx for this guide. Here are some observations as I work through it:

I didn't install XE into the default location (C:\oraclexe) but discovered right away that the Oracle XE install path can't include SPACE chars (flashback to DOS 3.1 days!), so I used "C:\progra~1\Oracle\XE" (I had previously installed Oracle 9i ODBC into "C:\progra~1\Oracle"). The install went ok. Using your guide (SUGGESTION: Allow for a "your OracleXE install directory" instead of assuming "C:\oraclexe"), I created a directory structure for a new database "OraXE-TmTrk" instead of "OraXE" (SUGGESTION: Warn about the connections between desired database name, dir name, SID name, pfile name, pfile db_name, init.ora file name, etc). Your instructions say something about a password file being created under the database directory, but doesn't state explicitly if the system or user does this.

After getting several steps down, I discovered another DOS limitation - no names longer than 8 chars! (SUGGESTION: Warn users about this). Another problem was that the pfile param in "startup nomount" needed quotes around it : 'startup nomount pfile="C:\...etc..." '. I changed the name to "OraXEtt" (assuming that the "-" would cause Oracle to blow it's stack at some point) and renamed/modified the dir, pfile, db_name, and ORACLE_SID, deleted the OraXe-TmTrk SID ("oradim -delete -SID OraXE-TmTrk") and created a new one. The instance started with numbers similiar to yours. The "create database" returned a control file error - I had a typo in my "initOraXEtt.ora" file. I corrected that by still had a problem. I had to shutdown the instance and restart it to get it to re-read the ".ora" file. After that, the db was successfully created, but the "create database" command is very confusing - Apparently I have to enter all those lines, not just the first. And after entering just the first line, it would be nice to know how to undo that. I eventually entered enough combinations of abort / shutdown / drop / mount / exclusive / restrict where I got something to happen.

Creating the data dictionary spews about a billion lines. It might be a good idea to have the user confirm the ORACLE_HOME environment var *BEFORE* running those 2 commands. The operation eventually stopped with this:
----
CREATE OR REPLACE PACKAGE utl_raw IS
*
ERROR at line 1:
ORA-06554: package DBMS_STANDARD must be created before using PL/SQL

ERROR:
ORA-00942: table or view does not exist
.
.
*
ERROR at line 1:
ORA-06553: PLS-213: package STANDARD not accessible
----

ah well, that was fun. Now where is the "uninstall"....

carlos mafla said...

Hi mnemotronic thanks a lot for your suggestions.


I didn't install XE into the default location (C:\oraclexe) but discovered right away that the Oracle XE install path can't include SPACE chars (flashback to DOS 3.1 days!), so I used "C:\progra~1\Oracle\XE" (I had previously installed Oracle 9i ODBC into "C:\progra~1\Oracle"). The install went ok. Using your guide (SUGGESTION: Allow for a "your OracleXE install directory" instead of assuming "C:\oraclexe"),

* The idea with "static names" was to try to make easier to follow the instructions and to have just one name to reference and less variables to deal with. This is just one way to create the database, and if you make little changes maybe you end up with different results as you figured out. The steps where intended to be very basic focusing on the main goal that was just to create the database with very basic instructions.


I created a directory structure for a new database "OraXE-TmTrk" instead of "OraXE" (SUGGESTION: Warn about the connections between desired database name, dir name, SID name, pfile name, pfile db_name, init.ora file name, etc).

* Ok, that´s one of the reasons why I used a particular name. I think is clear that the database name and SID should be the same (I commented that in the step 4), and that's the most important thing. You can name the init.ora file and dir name as you want (but you shouldn't do that as good practice), and the pfile is created based on the SID that you set in the shell.

Your instructions say something about a password file being created under the database directory, but doesn't state explicitly if the system or user does this.

* The password file is created after running the 'oradim' command. You can check the image in the step 3, it shows the file in the bottom left corner 'PWDoraXE.ora'


After getting several steps down, I discovered another DOS limitation - no names longer than 8 chars! (SUGGESTION: Warn users about this). Another problem was that the pfile param in "startup nomount" needed quotes around it : 'startup nomount pfile="C:\...etc..." '. I changed the name to "OraXEtt" (assuming that the "-" would cause Oracle to blow it's stack at some point) and renamed/modified the dir, pfile, db_name, and ORACLE_SID, deleted the OraXe-TmTrk SID ("oradim -delete -SID OraXE-TmTrk") and created a new one. The instance started with numbers similiar to yours. The "create database" returned a control file error - I had a typo in my "initOraXEtt.ora" file. I corrected that by still had a problem. I had to shutdown the instance and restart it to get it to re-read the ".ora" file. After that, the db was successfully created, but the "create database" command is very confusing - Apparently I have to enter all those lines, not just the first. And after entering just the first line, it would be nice to know how to undo that.

* Yes, I now that the create command has a lot of lines and can be very confusing, the idea was that anyone could copy and paste it in SQL*Plus. There are a lot topics that are not covered here like tablespaces, group files, etc. The lines you enter in SQL*Plus are kept in the sql buffer , you can use the 'edit' command to edit the buffer, use the 'change' command to change a line of the buffer or just 'clear buffer' command and start over, when is a small sql command I often just send the command to the server (with ;) without taking care of the errors and start over.


Tx again.

Carlos Mafla

oguzu said...

Hi

Thanks for cool solution.This article got me a key of understanding oracle basic architecture.

And I have one question.

When Runninng below command, I saw some "ORA-04031" error messages.

@?\rdbms\admin\catproc.sql

after creating database, I can create new tables on newly database,so I seemed to do well.

Can I egnore those error messages when run that command after creating database?

carlos mafla said...

I had this same issue before (I also posted this before) , I got a lot of ORA-00604 and ORA-04031 while running catalog.sql :

ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared
pool","select inst_id, plw...","Typecheck","seg:kggfaAllocSeg")


It Seems like by default oracle allocates 32M of shared_pool_size:


SQL> show parameters shared%

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
hi_shared_memory_address integer 0
max_shared_servers integer
shared_memory_address integer 0
shared_pool_reserved_size big integer 1677721
shared_pool_size big integer 32M
shared_server_sessions integer
shared_servers integer 0

and it's not enough to load the whole script. I increased the value to 64M in the initialization parameters and the scripts then ran without any error.

Anonymous said...

Hi all,
I have tried what you wrote for creating database. I could create my own database. However, I just did everything by using command line mode. Could you please tell me how can I manipulate on the database, e.g. create table, trigers, etc. with the GUI. I have tried with "Go to Database Home Page". However, this one is just for XE database, not my own new database.
Thank

shoaib ali said...

hi there
when i try to execute the create database command and add the code with it , it gives me error i.e

sysaux datafile 'c:\oracle\oradata\ab\sysaux.dbf'
error at line 12
ora-02165: invalid option for create database

Carlos said...
This comment has been removed by the author.
Carlos said...

hi,
You may have to check that the 'c:\oracle\oradata\ab\sysaux.dbf' path is correct, if you're using xe probably your path would start at c:\oraclexe

good luck

shoaib ali said...

The problem is persisting
the path i.e
sysaux datafile 'c:\oracle\oradata\ab\sysaux.dbf' seems to be correct
but the thing is that my ab folder in oradata is empty do i need to create any file there first ....?
please help

shoaib ali said...

hi carlos ,
i am stuck at this for a long time . i have to give my 1z0-031 exams pretty soon so please help......good luck

Anonymous said...

I tried to create a database using command prompt. Below command I used for this



create database demo
logfile
group 1 (
'd:\oracle\product\10.2.0\oradata\demo\redolog_g1_m1.rdo',
'd:\oracle\product\10.2.0\oradata\demo\redolog_g1_m2.rdo'
) size 102400K reuse,
group 2 (
'd:\oracle\product\10.2.0\oradata\demo\redolog_g2_m1.rdo',
'd:\oracle\product\10.2.0\oradata\demo\redolog_g3_m2.rdo'
) size 102400K reuse
datafile 'd:\oracle\product\10.2.0\oradata\demo\system_01.dbf' size 512000K reuse
extent management local
sysaux datafile 'd:\oracle\product\10.2.0\oradata\demo\sysaux.dbf' size 1048576k reuse
default temporary tablespace temp
tempfile 'd:\oracle\product\10.2.0\oradata\demo\temp_01.dbf' size 1048576k reuse
extent management local uniform size 1m
undo tablespace UNDOTBS1
datafile 'd:\oracle\product\10.2.0\oradata\demo\undo_01.dbf' size 1048576k reuse
;





After run this command it is giving a message "Database created "

After that we run the below scripts to create the data dictionaries
@%ORACLE_HOME%\rdbms\admin\catalog.sql
@%ORACLE_HOME%\rdbms\admin\catproc.sql

After ran those it showing this message "PL/SQL procedure successfully completed"

But it is not creating the new database entry in 'Oracle enterprise manager console'

Can somebody please help me on this problem.

kirsten said...

Hi. I am facing issues with the listener as well. When i run services.msc, i've found OracleXETNSListener started it, however it is still not listening to the database i've created. every step i've followed as posted on this blog but brings to no avail.

Is there a need to modify any C:\oraclexe\app\oracle\product\10.2.0\server\NETWORK\ADMIN\listener.ora or C:\oraclexe\app\oracle\product\10.2.0\server\NETWORK\ADMIN\sqlnet.ora or C:\oraclexe\app\oracle\product\10.2.0\server\NETWORK\ADMIN\tnsnames.ora?

p/s: Thanks for this blog. It helped me create the database but now i'm just facing issues with the listener.

kirsten said...

27-MAR-2008 19:03:10 * (CONNECT_DATA=(SID=TestDB)(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=50052)) * establish * TestDB * 12505
lefTNS-12505: TNS:listener does not currently know of SID given in connect descriptor


This was the C:\oraclexe\app\oracle\product\10.2.0\server\NETWORK\log\listener.log output when i've tried to connect using an oracle client.

carlos said...

Hi Kristen, If you followed the steps described here you should notice that the ORACLE_SID was called 'oraXE', I see in your log message the error :
'TNS:listener does not currently know of SID given in connect descriptor' and the ORACLE_SID shown is 'TestDB'.

So first check what ORACLE_SID did you use to create the windows service and then check what ORACLE_SID you actually set in your shell before trying to connect to oracle.

You can set your ORACLE_SID like this:

set ORACLE_SID=oraXE

or check the actual value:

echo %ORACLE_SID%

Good luck ;)

Anonymous said...

I think I have a functional database named XE. I've moved the old XE out of the way and installed a new database. The one thing that I first noticed there is no user.dbf and users.dbf files. Why?

Also when I try to connect to the database using the HTML link provided by Oracle install, I get page not found error. I rename the data directory back to the original, ithe page is found. I did a grep and found that sysaux.dbf and system.dbf seem to have 127.0.0.1 in there, so how do I add that to the new database DBF files?

THX!

Peter said...

excellent blog! very helpful. Just one comment.

it requires one more step to execute at the end. As user system (not sys) should be executed following script:

@?\sqlplus\admin\pupbld.sql

otherwise it complains when I connect with newly created users:

SQL> connect orabpel/orabpel
Error accessing PRODUCT_USER_PROFILE
Warning: Product user profile information not loaded!
You may need to run PUPBLD.SQL as SYSTEM
Connected.

anyway good job!

feiroz said...

Can i used these steps in oracle 10g standard edition.

Roxana Gabriela said...

Hi Carlos,
Thanx again for a very useful article. Unfortunately i got stuck close to the shore while executing
@?\rdbms\admin\catalog.sql

Indeed my shared_pool_size is 32. I tried to increase it:
alter system set shared_pool_size=64M;

but i get the flowing:
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-04033: Insufficient memory to grow pool

Do you have any advice? How did u manage to increase ur shared_pool_size?

Looking forward for ur answer

Cheers
Roxana

Anonymous said...

you don't write that we need to create the dir oradata/oraXE manually!

carlos said...

Sorry, but I think you should know how to create a directory in windows.

Anonymous said...
This comment has been removed by a blog administrator.
Brian said...

Awesome write up.. Its very helpful.

vivan said...

Hi,

Is it posible if I copy paste the old database from oracle 9.2 to oracle 10g XE manually?

I follow the step until step 5, I already create new SID and can connect/run the new instance/service, but I cannot login to database homepage.

I copy the database folder from "oracle/ora92/db_name" to oraclexe/oradata/db_name"

I try to login to homepage using username and password from default oracle 10gXE cannot, i try to login using username and password from the new ORACLE_SID also cannot, I try using id and pass from old database cannot.

What should i do? thanks.

Anonymous said...

Hi Carlos,

i am using Oracle 10g Express and server 2003 Sp2 i want to change the oracle sid from XE to SM7 i am following the steps .. .

i have encounter the problem that when i type

SQL>connect / as sysdba
ORA-12560 TNS protocol adapter error

how will i give it sysdba priviliges ?

Thanks,
-Mohsin

Anonymous said...

HI Carlos,

On this step

oradim -new -sid %ORACLE_SID% -intpwd passwordhere -startmode M

i get error and i think there will be start mode =auto ? and what about pfile? parameter

on this step i am getting error when i put start mode M

Unable to find error file %ORACLE_HOME%\RDBMS\opw.msb
Message 51 not found; No message file for product=RDBMS, facility=ORADIM

and when i put startmode auto then it gives me error

Unable to find error file %ORACLE_HOME%\RDBMS\opw.msb
Message 51 not found; No message file for product=RDBMS, facility=ORADIM

then let me know what is the problem ???

Regard,
Mohsin

Anonymous said...

Nice blog

BGeorge said...

Thanks a lot for the details. It is a very good tutorial to understand the basic architecture of oracle db. By the way, the create database command failed for me many time and finally I created the folder oraXE under the folder "C:\oraclexe\oradata\" and then the database got created. Is this necessary or the create database command will create the directory if it is not there? Please advise...

anand said...

hi,im working in xp.iam install a oracle then sql devloper.im creating a new database but im in fail.its show me the error is test fail lo exception. the netwrk adapter could not establish the coonection.plz show me the soloution of dis error

anand said...

im created in new data base but ican create dis.im using cmd
den i write sqlplus/as sysdba
its not conected wat can i do and mi window is xp

anand said...

im using in new connection a
connection name-abc
username-hr
passwrd-hr
host name-localhost
port-1521
sid-xe

plz tell me im right or nt

Krish said...

Good tutorial. Really Googled a lot time to find the perfect tutor.

Everything worked fine, except step 3 for me..

"oradim -new -sid %ORACLE_SID% -intpwd passwordhere -startmode M"

i used the following cmd

"oradim -new -sid mandb1 -syspwd sys -startmode manual -pfile F:\oracle\product\10.2.0\admin\mandb1\pfile\init.ora.3232010121242
"

Thanks for the wonderful guidelines.

Anonymous said...

Hemant :======

very nice 1 ...thanks a lot..


will u tell me hw to clone database using cold backup

my id is:

hakhandare@gmail.com

Anonymous said...

We need to set sga_target = 800M in the initXE.ora