DataGuard DB_NAME parameter
On 10.2 database,
Is it possible for DB_NAME parameter to be different in both Primary and Physical Standby databases?
I know DB_UNIQUE_NAME parameter must be different. But want to know whether DB_NAME can also be different.
Instances are distinguished by SID. Thus, two instances, particularly if running from the same ORACLE_HOME, have to have different SIDs if on the same server. However, Oracle has an additional check on DB_NAME as well. Two instances cannot have the same DB_NAME unless DB_UNIQUE_NAME is specified.
DB_NAME is always the same when you create a Physical Standby. You can't change the DB_NAME -- if you change the value in the init/spfile parameter file, a startup will error out because it checks the DB_NAME with that in the DataFile Headers. Since the DataFiles of a Physical Standby are a physical clone of the primary, the DB_NAME has to be the same. (the same applies for DBID -- the DBID of the Primary and the Standby are the same and that is why you have to be careful about using a common RMAN Repository for both databases -- there are MetaLink notes about how to do Standby Backups).
DB_UNIQUE_NAME doesn't get stored in the DataFile headers.
Hemant K Chitale
Similar Messages
-
Hi,
can someone educate me please, whats the purpose of the db_name parameter, can I for example use it as a connect string such as sqlplus user/password@oracle_sid and use instead sqlplus user/password@db_name?
Thanks899329 wrote:
Hi all,
can we change all the perameter in spfile using scope=spfile option. if yes, i am trying to change db_name but it is not getting change even though mentioned scope=spfile. andBecause this parameter can't be changed once the db is created. It would take just more than the spfile change if you are so willing. Have a look at the below link as one of the examples of how to proceed for it,
http://www.idevelopment.info/data/Oracle/DBA_tips/Database_Administration/DBA_7.shtml
how sga_target, sga_max_size, memory_target, memory_max_size parameter are spfile. values i given are not setting correctly.No idea what you meant here.
Aman....
PS: Do mention your db version in 4 digits along with your o/s information -
hello
i am setting up dataguard on 10g winxp,
i want that the standby database have the same name like the primary , but wouldnt that create a conflict in this parameter
LOG_ARCHIVE_CONFIG='DG_CONFIG=(chicago,boston)'
LOG_ARCHIVE_CONFIG='DG_CONFIG=(chicago,chicago)'
thanks?hello
i was reading the documentation its says that this parameter specifies the
DB_UNIQUE_NAME of the primary and standby databases
is that the same as their services names ?
thanks again -
Is db_name is the only parameter for creating database ? [Exper. on 32-bit]
Because of the discussion present in the following thread, I did few experiments and would you like to share with you. Hope it is a useful information for you guys.
Re: db_name & memory allocation
OS: Win XP SP2 or Windows 2000 <b>(32-bit)</b>
Oracle Version: Oracle 10gR2
System RAM: 1G
<b>Attempting to create the database CCC by specifying db_name parameter only</b>
C:\oracle\product\10.2.0\db_1\database>copy con initCCC.ora
db_name=CCC
^Z
1 file(s) copied.
<b> Starting the service </b>
C:\oracle\product\10.2.0\db_1\database>oradim -new -sid CCC -startmode m
Instance created.
C:\oracle\product\10.2.0\db_1\database>set oracle_sid=CCC
C:\oracle\product\10.2.0\db_1\database>sqlplus "/as sysdba"
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Apr 6 07:50:06 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL>
SQL>
SQL> startup nomount
ORACLE instance started.
Total System Global Area <b>113246208</b> bytes -- Default SGA size
Fixed Size 1247588 bytes
Variable Size 58721948 bytes
Database Buffers 50331648 bytes
Redo Buffers 2945024 bytes
<b> On seeing dynamic components size, shared pool got
33m, large pool got 0m, java pool got 25m and buffer cache
got 50m. Please check the references for these default
values. </b>
SQL> select component,current_size from v$sga_dynamic_components;
COMPONENT CURRENT_SIZE
shared pool 33554432
large pool 0
java pool 25165824
streams pool 0
DEFAULT buffer cache 50331648
KEEP buffer cache 0
RECYCLE buffer cache 0
DEFAULT 2K buffer cache 0
DEFAULT 4K buffer cache 0
DEFAULT 8K buffer cache 0
DEFAULT 16K buffer cache 0
COMPONENT CURRENT_SIZE
DEFAULT 32K buffer cache 0
ASM Buffer Cache 0
13 rows selected.
<b>Total=109051904 </b>
SQL>
create database
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
<b>Errors in alert log file</b>
ORA-00604: error occurred at recursive SQL level 1
<b>ORA-04031: unable to allocate 40 bytes of shared memory ("shared pool","create unique index
i_proxy_...","sql area","kksol : kksnsg")
</b>
Error 1519 happened during db open, shutting down database
USER: terminating instance due to error 1519
<b>It was thought that shared_pool memory area is not
sufficient. Then thought to know how oracle will behave on
setting sga_target parameter.</b>
<b>initCCC.ora</b>
db_name=CCC
sga_target=113m
SQL> startup nomount
ORACLE instance started.
Total System Global Area <b>121634816 bytes -- Got around 121m </b>
Fixed Size 1247636 bytes
Variable Size 54527596 bytes
Database Buffers 62914560 bytes
Redo Buffers 2945024 bytes
<b>Now create database statement got success here.
Instance got few extra Mbs of memory and oracle can create
the database.</b>
<b>Then it was thought that, why to give 121Mb even. Let exactly 113246208 bytes be devoted to the instance.</b>
initCCC.ora
db_name=CCC
sga_target=113246208 -- providing exact number of bytes as obtained in default case
SQL> startup nomount
ORACLE instance started.
Total System Global Area 113246208 bytes
Fixed Size 1247588 bytes
Variable Size 54527644 bytes
Database Buffers 54525952 bytes
Redo Buffers 2945024 bytes
SQL>
<b> Now create database statement got success here as
well. Because of sga_target, automatic shared memory
management enabled and instance was taking care of buffer
cache, shared pool, large pool, java pool and
streams_pool. In this case shared pool got 46m (greater
than default case value). Java pool and Large pool got 4
mb each and buffer cache got 54m. </b>
SQL> select component,current_size
2 from v$sga_dynamic_components;
COMPONENT CURRENT_SIZE
shared pool 46137344
large pool 4194304
java pool 4194304
streams pool 0
DEFAULT buffer cache 54525952
KEEP buffer cache 0
RECYCLE buffer cache 0
DEFAULT 2K buffer cache 0
DEFAULT 4K buffer cache 0
DEFAULT 8K buffer cache 0
DEFAULT 16K buffer cache 0
COMPONENT CURRENT_SIZE
DEFAULT 32K buffer cache 0
ASM Buffer Cache 0
13 rows selected.
<b>Total=109051904 </b>
SQL>
By providing 113246208 bytes (as in default case) of
memory to SGA by setting sga_target value, Oracle gave
extra memory to shared_pool and buffer cache than in case
of default, thus helping create database statement to get
pass. Oracle always recommends to use automatic shared
memory management by setting sga_target parameter value.
Hope this experiment provides few clues about automatic
shared memory management feature of Oracle 10g. This case
was conducted on 32-bit Oracle. It is quite possible that
create database statement might get success in 64-bit
Platform as by default Oracle will provide 84 Mb to Shared
pool. But to confirm, it has to be experimented.
References:
Shared pool
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams196.htm#sthref804
Large Pool
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams090.htm#sthref377
Java Pool
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams087.htm#sthref364
Buffer Cache
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams043.htm#sthref185Hi,
Good Work Mohammed !!!
Regards
Taj -
I am creating a Oracle 10g dataguard configuration within the same linux host. since DB_NAME parameter should be the same and DB_UNIQUE_NAME parameter should be different for both Primary and Standby databases, I am configuring the following things.
Primary
DB_NAME = ABC
DB_UNIQUE_NAME = ABC
INSTANCE_NAME = ABC
when connecting to primary database,
export ORACLE_SID = ABC
In Standby,
DB_NAME = ABC
DB_UNIQUE_NAME = XYZ
INSTANCE_NAME = XYZ
when connecting to standby database,
export ORACLE_SID = XYZ
Is this correct ? will this work for configuration within a single host ? or is there any problem with the above parameters ?
Oracle documentation tells about configuring dataguard in two hosts. But not within a single host.Is this correct ? will this work for configuration within a single host ? or is there any problem with the above parameters ?
yes its correct there is no different steps for DG implementation within the same node or diffrent node,excpet in 9i there you have to specify lock_name_space parameter when you want to open a copy database with the same DB_NAME on the same machine as the source database.
but in 10g new DB_UNIQUE_NAME attribute is introduced to clearly identify the relationship between a primary and standby databases.
Khurram -
DataGuard Broker in 11gR2 - StaticConnectIdentifier
Ok, I have read that in 11gR2 you no longer have the requirement of putting in a static entry in your listener.ora file with <SID>_DGMGRL if you use the Dataguard Broker parameter: StaticConnectIdentifier. I have used this new parameter and it was set up automatically to be:
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=DB1)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=prod_sb_DGMGRL)(INSTANCE_NAME=prod_sb)(SERVER=DEDICATED)))'
My question is that there is no entry anywhere that specifies the SERVICE_NAME as prod_sb_DGMGRL. Will my switchover work without that SERVICE_NAME being defined no where? Am I missing a step? Thanks folks.Hello;
I'm thinking the switchover will fail with an ORA-12514. Without the listener.ora entry DGMGRL will not be able to connect to the databases after they have been stopped.
So you still need the _DGMGRL or at least a static entry in the listener.ora. In any event the static entry will not cause an issue.
*Switchover Failed With ORA-12521 using Dataguard Broker [ID 1380949.1]*
For additional information see - 8.3.40 StaticConnectIdentifier in "Data Guard Broker 11g Release 2 (11.2) E17023-04"
"A connect identifier that refers to a service that is statically registered"
Best Regards
mseberg
Edited by: mseberg on Sep 20, 2012 4:04 AM -
LK DB_NAME FILE에 대하여 (ORA-1102에 대한 원인 설명)
제품 : ORACLE SERVER
작성날짜 : 2000-05-05
LK<DB_NAME> FILE에 대하여 (ORA-1102에 대한 원인 설명)
===================================================
Unix 용 Oracle7.3.3 이전의 version에서는 parallel server mode(OPS)로
운용하지 않더라도 서로 다른 ORACLE_SID를 이용하는 두개의 instance가 하나의
database를 동시에 mount하는 것이 경우에 따라서는 가능할 수도 있었다
(<Bug:272030>). 이 경우, 서로 독립적인 두개의 instance가 동일한 database
file들을 동기화 (synchronisation)없이 access할 수 있기 때문에 database
corruption을 유발시킬 수 있었다.
Unix system에서의 이러한 문제를 회피하기 위하여 7.3.3부터 'mount lock'
file이 이용된다. 이 file은 그 size가 0 byte, 생성되는 위치는
$ORACLE_HOME/dbs 이며 그 이름은 lk<DB_NAME> 이다.
Oracle이 database를 mount할 때 lk<DB_NAME> file과 관련하여 다음과 같은
절차를 수행한다.
1. file name의 'DB_NAME' 부분은 db_name parameter를 이용한다.
예를 들어, db_name=V803 이라면 사용되는 lock file의 위치와 이름은
'$ORACLE_HOME/dbs/lkV803'이 된다.
2. 만약 해당 file이 존재하지 않는다면 생성한다.
존재한다면 file을 open한다.
3. 이 file에 exclusive Unix file lock을 설정한다.
위의 과정 상에서 문제가 발생된다면 해당 instance는 db를 mount할 수 없으며
ORA-1102('cannot mount database in exclusive mode')가 return된다.
Releasae 7.3.3 이전에서는 동일한 $ORACLE_HOME, 동일한 db_name을 이용하는
두 개의 database를 $ORACLE_SID만 다르다면 동시에 open하여 사용할 수 있었다.
그러나 lock file이 사용되는 7.3.3부터는, lock file의 이름에 db_name이
이용되기 때문에 어느 한쪽의 db_name을 변경해야만 동시에 open하여 사용할
수가 있다.(db_name의 변경은 controlfile을 재생성함으로써 가능하다.)
이렇게 database의 db_name이 변경되면 각각의 lk<DB_NAME> file을 생성하여
이용하게 된다.
참고 사항
1. database를 구동하고 있는 instance가 있을 때에는 lk<DB_NAME> file은
삭제하지 않도록 한다.
2. database가 shutdown되더라도 lk<DB_NAME> file은 삭제되지 않고 존재한다.
따라서 이 file의 유무를 가지고 database의 구동 유무를 판단할 수 없다.
3. lk<DB_NAME>의 DB_NAME은 SID와는 다를 수 있다. SID가 아닌 DB_NAME을
이용함에 주의.
4. lock file과 관련하여 다음의 error들이 발생될 수 있다.
ORA-9992 scumnt: failed to open <FILENAME>
ORA-9993 scumnt: failed to lock <FILENAME>
ORA-1102 cannot mount database in exclusive mode -
Database Instance Installation Problem on Oracle 8.1.7
Dear gurus,
I'm having problem when installing Database Central Instance on Solaris 10 - Oracle 8.1.7 (32bit) - SAP 4.6c.
Here's the error log:
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Connected.
Echo ON
SVRMGR> SET TERMOUT ON;
Termout ON
SVRMGR> SHUTDOWN ABORT;
ORACLE instance shut down.
SVRMGR> STARTUP NOMOUNT PFILE=init.ora;
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 1
Additional information: 3
SVRMGR> CREATE DATABASE PRD
2> CONTROLFILE REUSE
3> MAXDATAFILES 254
4> MAXLOGFILES 255
5> MAXLOGHISTORY 1000
6> MAXLOGMEMBERS 3
7> MAXINSTANCES 50
8> CHARACTER SET "WE8DEC"
9> DATAFILE
10> '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 300M REUSE
11> NOARCHIVELOG
Info: DBCREATEDB_IND_ORA SvrmgrDoDummy 2 349
12> LOGFILE
13> GROUP 11 (
14> '/oracle/PRD/origlogA/log_g11m1.dbf',
15> '/oracle/PRD/mirrlogA/log_g11m2.dbf'
16> ) SIZE 20M REUSE
17> ,GROUP 13 (
18> '/oracle/PRD/origlogA/log_g13m1.dbf',
19> '/oracle/PRD/mirrlogA/log_g13m2.dbf'
20> ) SIZE 20M REUSE
21> ,GROUP 12 (
22> '/oracle/PRD/origlogB/log_g12m1.dbf',
23> '/oracle/PRD/mirrlogB/log_g12m2.dbf'
24> ) SIZE 20M REUSE
25> ,GROUP 14 (
26> '/oracle/PRD/origlogB/log_g14m1.dbf',
27> '/oracle/PRD/mirrlogB/log_g14m2.dbf'
28> ) SIZE 20M REUSE
29> ;
CREATE DATABASE PRD
ORA-01034: ORACLE not available
SVRMGR> EXIT
Server Manager complete.
Error: DBCREATEDB_IND_ORA InternalInstallationDo 2 349
Create Database failed errorcode = 27123.
Error: DBCREATEDB_IND_ORA InstallationDo 2 349
Phase failed.
Error: Main {} 2 349
Installation aborted.
I have tweaked the shared memory max as suggested in Oracle Manual / SAP Installation Guide, to no avail.
The listener is up already.
When I logged in as user ORA<SID>, and go to svrmgrl > startup nomount pfile=init.ora, it can startup without hassle.
Although the Product is not supported in PAM, we have another machine running smoothly for years with this product combination, so it's not the product compatibility issues.
But when using R3SETUP -f DATABASE.R3S, the phase stopped with the log pasted above.
Any ideas, gurus?
Thanks for help.
Best Regards,Mr. Markus, there's no file on saptrace/usertrace.
To be sure, here's what I've done:
1. Run oracle listener.
2. Check connection with svrmgrl > connect internal (connected).
3. Modify init.ora with my DB Name:
wef
# replace DEFAULT with your database name
*db_name=PRDDB*
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# 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 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# 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
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
3. set shared memory parameter as in sapnote 724713.
4. executing R3SETUP
and it tells me this error:
Info: DBCREATEROLLSEGSTART_IND_ORA SyGroupIDGet 2 354
Group id for group dba is 102.
Info: DBCREATEROLLSEGSTART_IND_ORA SyUserIDGet 2 354
User id for user oraprd is 100.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Return from DB: 1034.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
Server Manager complete.
Info: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database.
Info: DBCREATEROLLSEGSTART_IND_ORA OracleCmd 2 354
Startup Database with PFILE: init.ora.
Info: DBCREATEROLLSEGSTART_IND_ORA SyCoprocessCreateAsUser 2 354
Creating coprocess /oracle/PRD/817_32/bin/svrmgrl [email protected] as user oraprd and group dba ...
Info: DBCREATEROLLSEGSTART_IND_ORA SyGroupIDGet 2 354
Group id for group dba is 102.
Info: DBCREATEROLLSEGSTART_IND_ORA SyUserIDGet 2 354
User id for user oraprd is 100.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Return from DB: 27123.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Connected.
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 1
Additional information: 2
alter database noarchivelog
ORA-01034: ORACLE not available
alter database open
ORA-01034: ORACLE not available
Server Manager complete.
Error: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database with error: 27123.
Error: DBCREATEROLLSEGSTART_IND_ORA InstallationDo 2 354
Phase failed.
Error: Main {} 2 354
Installation aborted.
It's driving me nuts for the last days.. can't figure out what happened here. -
EM 10g - Listener does not show up on DB home, but is running. Why??
Oracle Version 10.2.0.1.0
Microsoft Windows Server 2003 R2 Server 5.2 Service Pack 2 (32-bit)
LSNRCTL> start LISTENER
Starting tnslsnr: please wait...
TNSLSNR for 64-bit Windows: Version 10.2.0.1.0 - Production
System parameter file is D:\oracle\product\10.2.0\db_1\network\admin\listener.ora
Log messages written to D:\oracle\product\10.2.0\db_1\network\log\listener.log
Trace information written to D:\oracle\product\10.2.0\db_1\network\trace\listener.trc
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=us-as1.nti2.org)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 10.2.0.1.0 - Production
Start Date 22-OCT-2007 11:42:18
Uptime 0 days 0 hr. 0 min. 5 sec
Trace Level user
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File D:\oracle\product\10.2.0\db_1\network\admin\listener.ora
Listener Log File D:\oracle\product\10.2.0\db_1\network\log\listener.log
Listener Trace File D:\oracle\product\10.2.0\db_1\network\trace\listener.trc
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=us-as1.nti2.org)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
========================================================
LSNRCTL> status LISTENER
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 10.2.0.1.0 - Production
Start Date 22-OCT-2007 11:42:18
Uptime 0 days 0 hr. 14 min. 8 sec
Trace Level user
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File D:\oracle\product\10.2.0\db_1\network\admin\listener.ora
Listener Log File D:\oracle\product\10.2.0\db_1\network\log\listener.log
Listener Trace File D:\oracle\product\10.2.0\db_1\network\trace\listener.trc
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=us-as1.nti2.org)(PORT=1521)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "orcl.us-as1.nti2.org" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orclXDB.us-as1.nti2.org" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orcl_XPT.us-as1.nti2.org" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
The command completed successfully
======================================================
C:\Documents and Settings\pierrel>netstat -a
Active Connections
Proto Local Address Foreign Address State
TCP us-as1:smtp us-as1.nti2.org:0 LISTENING
TCP us-as1:http us-as1.nti2.org:0 LISTENING
TCP us-as1:nntp us-as1.nti2.org:0 LISTENING
TCP us-as1:epmap us-as1.nti2.org:0 LISTENING
TCP us-as1:microsoft-ds us-as1.nti2.org:0 LISTENING
TCP us-as1:nntps us-as1.nti2.org:0 LISTENING
TCP us-as1:kpop us-as1.nti2.org:0 LISTENING
TCP us-as1:1110 us-as1.nti2.org:0 LISTENING
TCP us-as1:1111 us-as1.nti2.org:0 LISTENING
TCP us-as1:1117 us-as1.nti2.org:0 LISTENING
TCP us-as1:1119 us-as1.nti2.org:0 LISTENING
TCP us-as1:1158 us-as1.nti2.org:0 LISTENING
TCP us-as1:1521 us-as1.nti2.org:0 LISTENING
==================================================
init.ora
# $Header: init.ora 25-jul-01.18:03:38 rajayar Exp $
# Copyright (c) 1991, 2001, Oracle Corporation. All rights reserved. */
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, use the
# same file for all instance. Place all instance-specific parameters
# at the end of the file using the <sid>.<parameter_name> = <value> syntax.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified differently for each instance, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own.
# replace "clustdb" with your database name
db_name = clustdb
compatible=9.0.0
db_files = 1024 # INITIAL
#INITIAL
#db_files=80
#SMALL
#DB_files=400
#MEDIUM
#db_files=1000
#LARGE
control_files = ("\\.\clustdb_control1", "\\.\clustdb_control2")
db_file_multiblock_read_count = 8 # INITIAL
# db_file_multiblock_read_count = 8
#SMALL
#db_file_multiblock_read_count = 16
#MEDIUM
#db_file_multiblock_read_count = 32
#LARGE
#Datawarehouse
db_block_size=8192
# Transaction processing
# db_block_size=4096
open_cursors=300
#Transaction processing
#sort_area_size=524288
#Datawarehouse
sort_area_size=1048576
large_pool_size=1048576 #Transaction processing, Datawarehouse
db_cache_size=50331648 #Datawarehouse, Transaction processing
java_pool_size=67108864 #Datawarehouse, Transaction processing
# db_block_buffers = 200 # INITIAL
# db_block_buffers=100 #SMALL
# db_block_buffers =550 # MEDIUM
# db_block_buffers=3200 #LARGE
#shared_pool_size = 52428800 # INITIAL
shared_pool_size = 67108864 # datewarehouse, transaction processing
log_checkpoint_interval = 10000
processes = 59 # INITIAL
# processes = 50
#SMALL
#processes = 100
#MEDIUM
#processes = 200
#LARGE
parallel_max_servers = 5
#SMALL
# parallel_max_servers = 4 x (number of CPUs)
#MEDIUM
# parallel_max_servers = 4 x (number of CPUs)
# LARGE
log_buffer = 8192 # INITIAL
#log_buffer = 8192
#SMALL
#log_buffer = 32768
#MEDIUM
#log_buffer = 163840
#LARGE
# 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 10 K each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = %ORACLE_HOME%/admin/clustdb/arch
# log_archive_format = "%%ORACLE_SID%%T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form at the end of this file:
# <sid>.rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/10 = 4:
# transactions = 40
# transactions_per_rollback_segment = 10
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# 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
# define directories to store trace and alert files
background_dump_dest=%ORACLE_HOME%/admin/clustdb/bdump
user_dump_dest=%ORACLE_HOME%/admin/clustdb/
db_block_size = 4096
remote_login_passwordfile = exclusive
# text_enable = TRUE
# The following parameters are needed for the Advanced Replication Option
job_queue_processes = 2
# job_queue_processes = 4 #datawarehouse
# job_queue_interval = 10
# job_queue_keep_connections = false
distributed_transactions = 5
open_links = 4
# The following parameters are instance-specific parameters that are
# specified for two instances named clustdb1 and clustdb2
undo_management=AUTO # For automatic undo management
# = MANUAL For manual/RBS undo management
cluster_database= true
cluster_database_instances=2
remote_listener=LISTENERS_CLUSTDB
# First instance specific parameters
clustdb1.thread=1
clustdb1.instance_name=clustdb1
clustdb1.instance_number=1
clustdb1.local_listener=listener_clustdb1
clustdb1.remote_login_passwordfile = exclusive
# Comment out clustdb1.undo_tablespace and uncomment clustdb1.rollback_segments
# when undo_management=MANUAL
clustdb1.undo_tablespace = UNDOTBS1
# clustdb1.rollback_segments = (rbs1_1,rbs1_2)
# Second instance specific parameters
clustdb2.thread=2
clustdb2.instance_name = clustdb2
clustdb2.instance_number = 2
clustdb2.local_listener = listener_clustdb2
clustdb2.remote_login_passwordfile = exclusive
# Comment out clustdb2.undo_tablespace and uncomment clustdb2.rollback_segments
# when undo_management=MANUAL
clustdb2.undo_tablespace = UNDOTBS2
# clustdb2.rollback_segments = (rbs2_1,rbs2_2)
===========================================
listener.ora
# listener.ora Network Configuration File: D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = D:\oracle\product\10.2.0\db_1)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = us-as1.nti2.org)(PORT = 1521))
TRACE_LEVEL_LISTENER = USER
===============================================
sqlnet.ora
# sqlnet.ora Network Configuration File: D:\oracle\product\10.2.0\db_1\network\admin\sqlnet.ora
# Generated by Oracle configuration tools.
# This file is actually generated by netca. But if customers choose to
# install "Software Only", this file wont exist and without the native
# authentication, they will not be able to connect to the database on NT.
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
=================================================
tnsnames.ora
# tnsnames.ora Network Configuration File: D:\oracle\product\10.2.0\db_1\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = us-as1.nti2.org)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl.us-as1.nti2.org)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
============================================================Enterprise manager still requires a static service definition in listener.ora and does not rely on dynamic registration.
From documentation:
The SID_LIST is required for backward compatibility with Oracle8 or Oracle7 databases, as well as external procedures and heterogeneous services, and some management tools, including Oracle Enterprise Manager.
Werner -
How do I create multiple databases on the same ORACLE_HOME
Hi,
I would like to know how can I create 2 databases on the same ORACLE_HOME? Also is it possible to start both databases at the same time?
When I installed oracle,a directory named database has been created under ORACLE_HOME, which contains all initorc1.ora ,etc ?
At this point how do I create another database named orc2 on the same machine?
Thanks in advance.
winnie philip.Hi,
Set the oracle_sid=db1
Now rename your init.ora to init<oracle_sid>.ora in $oracle_home/dbs directory.
Change the db_name parameter to appropriate name in the init<oracle_sid>.ora file.
Now create the database.
In the same fashion create another database with the new database name and different oracle_sid
Now in order to switch between the databases.
Change the env variable Oracle_Sid to the value of the database which you wanted to start.
Regards
Anand -
Unable to find the utl_file_directory option in init.ora
Hi all these are the contents of init.ora file in nacedell server.i did'nt find any thing as utl_file_directory to update with my directory created through sql*plus using
command
create directory dir as 'c:\dir';
here are the contents of init.ora file
cat init.ora command is giving contents as
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=DEFAULT
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# 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 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# 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
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
$There are strange things in the file you posted, are you sure that's your init.ora ? where did you find it ?
Moreover, you use "cat" to list the file, but you name "c:\dir" the directory : what is your OS ?
Furthermore, if you use directories, then you don't need to set utl_file_dir in init.ora, and directories don't show up within parameters, you can see them by
SQL> select * from all_directories; -
Restore spfile from rman backup ---- error.
Hi,
I am trying to execute recovery on new machine ...
I have done the following steps..
I have one database as ora10g2 as peroduction database on one machine as hosta
I have created a catalog on another machine cora10g2 (hostb)
I have taken a full backup from hosta as per following ...
the following command execute from hosta machine.
$ rman target sys/<passwd>@ora10g2 catalog rman/rman@cora10g2 ...
Backup completed ...
Now I am trying to restore this backup on hostb machine where i have already rman catlog database ..
I have done the following setting ...on host b
set oracle_sid=DUP
and execute following command ...
rman target / catalog rman/rman@cora10g2
RMAN> set dbid 2760732370
executing command: SET DBID
database name is "BAAN10G2" and DBID is 2760732370
RMAN>
RMAN>
RMAN> startup force nomount ;
startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/oracle/dbs/baan10g2/dbs/initbaan10g2.ora'
starting Oracle instance without parameter file for retrival of spfile
Oracle instance started
Total System Global Area 159383552 bytes
Fixed Size 1977112 bytes
Variable Size 67114216 bytes
Database Buffers 83886080 bytes
Redo Buffers 6406144 bytes
RMAN>
RMAN>
RMAN>
RMAN> show all ;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/backup/control/cntrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/baanora3/rman/ora10g2/bkup_db_%d_s%s_P%p_t%t' MAXPIECESIZE 1024;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
RMAN>
RMAN>
RMAN> list backup of spfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
2420 Full 7.33M DISK 00:00:01 14-JUN-07
BP Key: 2426 Status: AVAILABLE Compressed: NO Tag: TAG20070614T182935
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070614-00
SPFILE Included: Modification time: 14-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2509 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2515 Status: AVAILABLE Compressed: NO Tag: TAG20070615T130416
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-00
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2694 Full 7.33M DISK 00:00:01 15-JUN-07
BP Key: 2739 Status: AVAILABLE Compressed: NO Tag: TAG20070615T131703
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-01
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2760 Full 80.00K DISK 00:00:01 15-JUN-07
BP Key: 2763 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163437
Piece Name: /rman/spfile/spfile.ora
SPFILE Included: Modification time: 15-JUN-07
BS Key Type LV Size Device Type Elapsed Time Completion Time
2769 Full 7.33M DISK 00:00:02 15-JUN-07
BP Key: 2771 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163441
Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-02
SPFILE Included: Modification time: 15-JUN-07
RMAN>
RMAN>
RMAN> restore spfile from autobackup ;
Starting restore at 19-JUN-07
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=36 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=35 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=34 devtype=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: sid=33 devtype=DISK
channel ORA_DISK_1: looking for autobackup on day: 20070619
channel ORA_DISK_1: looking for autobackup on day: 20070618
channel ORA_DISK_1: looking for autobackup on day: 20070617
channel ORA_DISK_1: looking for autobackup on day: 20070616
channel ORA_DISK_1: looking for autobackup on day: 20070615
channel ORA_DISK_1: looking for autobackup on day: 20070614
channel ORA_DISK_1: looking for autobackup on day: 20070613
channel ORA_DISK_1: no autobackup in 7 days found
channel ORA_DISK_2: looking for autobackup on day: 20070619
channel ORA_DISK_2: looking for autobackup on day: 20070618
channel ORA_DISK_2: looking for autobackup on day: 20070617
channel ORA_DISK_2: looking for autobackup on day: 20070616
channel ORA_DISK_2: looking for autobackup on day: 20070615
channel ORA_DISK_2: looking for autobackup on day: 20070614
channel ORA_DISK_2: looking for autobackup on day: 20070613
channel ORA_DISK_2: no autobackup in 7 days found
channel ORA_DISK_3: looking for autobackup on day: 20070619
channel ORA_DISK_3: looking for autobackup on day: 20070618
channel ORA_DISK_3: looking for autobackup on day: 20070617
channel ORA_DISK_3: looking for autobackup on day: 20070616
channel ORA_DISK_3: looking for autobackup on day: 20070615
channel ORA_DISK_3: looking for autobackup on day: 20070614
channel ORA_DISK_3: looking for autobackup on day: 20070613
channel ORA_DISK_3: no autobackup in 7 days found
channel ORA_DISK_4: looking for autobackup on day: 20070619
channel ORA_DISK_4: looking for autobackup on day: 20070618
channel ORA_DISK_4: looking for autobackup on day: 20070617
channel ORA_DISK_4: looking for autobackup on day: 20070616
channel ORA_DISK_4: looking for autobackup on day: 20070615
channel ORA_DISK_4: looking for autobackup on day: 20070614
channel ORA_DISK_4: looking for autobackup on day: 20070613
channel ORA_DISK_4: no autobackup in 7 days found
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/19/2007 18:00:13
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
RMAN>
I am not able to restore spfile from rman backup ;;;Hi,
I would like to know few things
1. How are you setting the db_name ? you can set db_id at RMAN, how are you setting the db_name ?
2. Do you have any default init file at default location ? if yes, is the db_name parameter set correctly in that file ?
Since spfile is yet to be restored, you must set the db_name parameter correctly before you start spfile restore.This can be done with init file at default location which can even contain just one paremeter i.e db_name. -
Hi
database name CLONESQL(duplicate database) does not match parameter db_name ORCL4 (source database) where should i change this one
RMAN> duplicate target database to CLONESQL;
Starting Duplicate Db at 12-SEP-11
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=97 device type=DISK
contents of Memory Script:
set until scn 923880;
set newname for datafile 1 to
"/u01/app/oracle/oradata/CLONESQLo1_mf_system_76tvgsh1_.dbf";
set newname for datafile 2 to
"/u01/app/oracle/oradata/CLONESQLo1_mf_sysaux_76tvgsjg_.dbf";
set newname for datafile 3 to
"/u01/app/oracle/oradata/CLONESQLo1_mf_undotbs1_76tvgsqn_.dbf";
set newname for datafile 4 to
"/u01/app/oracle/oradata/CLONESQLo1_mf_users_76tvgsxh_.dbf";
set newname for datafile 5 to
"/u01/app/oracle/oradata/CLONESQLo1_mf_example_76tvstov_.dbf";
set newname for datafile 6 to
"/u01/app/oracle/oradata/CLONESQLrman01.dbf";
restore
clone database
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 12-SEP-11
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/CLONESQLo1_mf_system_76tvgsh1_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/CLONESQLo1_mf_sysaux_76tvgsjg_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/CLONESQLo1_mf_undotbs1_76tvgsqn_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/CLONESQLo1_mf_users_76tvgsxh_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/CLONESQLo1_mf_example_76tvstov_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /u01/app/oracle/oradata/CLONESQLrman01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area/ORCL4/backupset/2011_09_12/o1_mf_nnndf_TAG20110912T121122_76v1mbyr_.bkp
channel ORA_AUX_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area/ORCL4/backupset/2011_09_12/o1_mf_nnndf_TAG20110912T121122_76v1mbyr_.bkp tag=TAG20110912T121122
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:02:19
Finished restore at 12-SEP-11
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CLONESQL" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( '/u01/app/oracle/oradata/CLONESQL/onlielogo1_mf_1_76tvr06l_.log', '/u01/app/oracle/flash_recovery_area/CLONESQL/onlinelog/o1_mf_1_76tvr4pp_.log' ) SIZE 50 M REUSE,
GROUP 2 ( '/u01/app/oracle/oradata/CLONESQL/onlielogo1_mf_2_76tvr940_.log', '/u01/app/oracle/flash_recovery_area/CLONESQL/onlinelog/o1_mf_2_76tvrf5y_.log' ) SIZE 50 M REUSE,
GROUP 3 ( '/u01/app/oracle/oradata/CLONESQL/onlielogo1_mf_3_76tvrl7w_.log', '/u01/app/oracle/flash_recovery_area/CLONESQL/onlinelog/o1_mf_3_76tvrrpm_.log' ) SIZE 50 M REUSE
DATAFILE
'/u01/app/oracle/oradata/CLONESQLo1_mf_system_76tvgsh1_.dbf'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 2 switched to datafile copy
input datafile copy RECID=1 STAMP=761683828 file name=/u01/app/oracle/oradata/CLONESQLo1_mf_sysaux_76tvgsjg_.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=2 STAMP=761683828 file name=/u01/app/oracle/oradata/CLONESQLo1_mf_undotbs1_76tvgsqn_.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=3 STAMP=761683828 file name=/u01/app/oracle/oradata/CLONESQLo1_mf_users_76tvgsxh_.dbf
datafile 5 switched to datafile copy
input datafile copy RECID=4 STAMP=761683828 file name=/u01/app/oracle/oradata/CLONESQLo1_mf_example_76tvstov_.dbf
datafile 6 switched to datafile copy
input datafile copy RECID=5 STAMP=761683828 file name=/u01/app/oracle/oradata/CLONESQLrman01.dbf
contents of Memory Script:
set until scn 923880;
recover
clone database
delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 12-SEP-11
using channel ORA_AUX_DISK_1
starting media recovery
archived log for thread 1 with sequence 4 is already on disk as file /u01/app/oracle/flash_recovery_area/ORCL4/archivelog/2011_09_12/o1_mf_1_4_76v1q11f_.arc
archived log for thread 1 with sequence 5 is already on disk as file /u01/app/oracle/flash_recovery_area/ORCL4/archivelog/2011_09_12/o1_mf_1_5_76vdyn6f_.arc
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL4/archivelog/2011_09_12/o1_mf_1_4_76v1q11f_.arc thread=1 sequence=4
archived log file name=/u01/app/oracle/flash_recovery_area/ORCL4/archivelog/2011_09_12/o1_mf_1_5_76vdyn6f_.arc thread=1 sequence=5
media recovery complete, elapsed time: 00:00:05
Finished recover at 12-SEP-11
contents of Memory Script:
shutdown clone immediate;
startup clone nomount ;
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
startup failed: ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u01/app/oracle/product/11.1.0/db_1/dbs/initCLONESQL.ora'
starting Oracle instance without parameter file for retrieval of spfile
Oracle instance started
Total System Global Area 158662656 bytes
Fixed Size 2142496 bytes
Variable Size 79695584 bytes
Database Buffers 71303168 bytes
Redo Buffers 5521408 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CLONESQL" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 ( '/u01/app/oracle/oradata/CLONESQL/onlielogo1_mf_1_76tvr06l_.log', '/u01/app/oracle/flash_recovery_area/CLONESQL/onlinelog/o1_mf_1_76tvr4pp_.log' ) SIZE 50 M REUSE,
GROUP 2 ( '/u01/app/oracle/oradata/CLONESQL/onlielogo1_mf_2_76tvr940_.log', '/u01/app/oracle/flash_recovery_area/CLONESQL/onlinelog/o1_mf_2_76tvrf5y_.log' ) SIZE 50 M REUSE,
GROUP 3 ( '/u01/app/oracle/oradata/CLONESQL/onlielogo1_mf_3_76tvrl7w_.log', '/u01/app/oracle/flash_recovery_area/CLONESQL/onlinelog/o1_mf_3_76tvrrpm_.log' ) SIZE 50 M REUSE
DATAFILE
'/u01/app/oracle/oradata/CLONESQLo1_mf_system_76tvgsh1_.dbf'
CHARACTER SET WE8MSWIN1252
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 09/12/2011 18:51:07
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01504: database name 'CLONESQL' does not match parameter db_name 'ORCL4'
Thank youYou should change the DB_NAME parameter in the initial configuration (init<SID>.ora) file for the clone database before startup to CLONESQL.
Otherwise, show us the initial parameters for both source and clone.here is my parameter file
orcl4.ora
orcl4.__db_cache_size=385875968
orcl4.__java_pool_size=12582912
orcl4.__large_pool_size=4194304
orcl4.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
orcl4.__pga_aggregate_target=390070272
orcl4.__sga_target=578813952
orcl4.__shared_io_pool_size=0
orcl4.__shared_pool_size=167772160
Thank you
orcl4.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/orcl4/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/ORCL4/controlfile/o1_mf_76tvqvnw_.ctl','/u01/app/oracle/flash_recovery_area/ORCL4/controlfile/o1_mf_76tvqwmf_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_name='orcl4'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orcl4XDB)'
*.log_archive_format='%t_%s_%r.dbf'
*.memory_target=965738496
*.open_cursors=300
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.undo_tablespace='UNDOTBS1'
initclonesql.ora
db_name='CLONESQL'
db_block_size=8192
compatible='11.1.0.0.0'
remote_login_passwordfile='EXCLUSIVE'
control_files='/u01/app/oracle/oradata/CLONESQL/controlfile/o1_mf_76tvqvnw_.ctl','/u01/app/oracle/flash_recovery_area/CLONESQL/controlfile/o1_mf_76tvqwmf_.ctl'
db_file_name_convert = ('/u01/app/oracle/oradata/ORCL4/datafile/','/u01/app/oracle/oradata/CLONESQL')
log_file_name_convert = ('/u01/app/oracle/oradata/ORCL4/onlinelog/','/u01/app/oracle/oradata/CLONESQL/onlielog','/u01/app/oracle/flash_recovery_area/ORCL4/onlinelog','/u01/app/oracle/flash_recovery_area/CLONESQL/onlinelog') -
How to change the SID name in the server
hi all,
i installed oracle 10g R1 on windows 2003 server. i gave an sid and created a database. the database is new and there is no data in the db. now i want to change the SID name of the database. pls help me in doing this.
regards,
nagarjunaHi,
Just a notice: SID and DBNAME are two different things. But the usual practice is to have SID = DBNAME, so let me assume you want to change both SID and DBNAME.
Either you can do it manually by recreating the controlfile as orawiss suggests. You may discover some challenges around the way (for instance, for the command CREATE CONTROLFILE SET "new_dbname" to work, you have do delete or rename the old controlfiles first).
Or, you can change it easier by using nid utility. The detailed howto and all implications can be found on:
http://download.oracle.com/docs/cd/B14117_01/server.101/b10825/dbnewid.htm
Basically:
SQL> create pfile from spfile;
SQL> shutdown immediate;
nid TARGET=sys/password@oldname DBNAME=newname
copy the initoldname.ora to initnewname.ora and edit the DB_NAME parameter to reflect the new name
sqlplus / as sysdba
SQL> create spfile from pfile;
SQL>startup mount;
SQL> alter database open resetlogs;
Then don't forget to generate new password file for the new dbname (using orapw) and make changes in tnsnames.ora and listener.ora if needed.
Just make sure, the database has been properly shut down before changing the db_name either manualy by recreating controlfile or by the newid utility, as the renamed database has to be opened with resetlogs - making any crash recover of improperly shut down database impossible.
Kind regards,
Martin -
Oracle not starting up throwing error
My listener problem is solved but the DB dosent start up and throws this error, I also have a dump of the startup.log and the copy of init.ora file.
[oracle@localhost ~]$ ./oracle.sh start
Starting Oracle: Password:
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 24-DEC-2009 23:01:32
Copyright (c) 1991, 2005, Oracle. All rights reserved.
TNS-01106: Listener using listener name LISTENER has already been started
Password:
Failed to auto-start Oracle Net Listene using /ade/vikrkuma_new/oracle/bin/tnslsnr
Processing Database instance "sales": log file /u01/app/oracle/oracle/product/10.2.0/db_1/startup.log
OK
startup.log
/u01/app/oracle/oracle/product/10.2.0/db_1/bin/dbstart: Starting up database "sales"
Thu Dec 24 23:02:00 IST 2009
logger: Can't find init file for Database instance "sales".
logger: Error: Database instance "sales" NOT started.
init.ora
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
# init.ora
# FUNCTION
# NOTES
# MODIFIED
# atsukerm 08/06/98 - fix for 8.1.
# hpiao 06/05/97 - fix for 803
# glavash 05/12/97 - add oracle_trace_enable comment
# hpiao 04/22/97 - remove ifile=, events=, etc.
# alingelb 09/19/94 - remove vms-specific stuff
# dpawson 07/07/93 - add more comments regarded archive start
# maporter 10/29/92 - Add vms_sga_use_gblpagfile=TRUE
# jloaiza 03/07/92 - change ALPHA to BETA
# danderso 02/26/92 - change db_block_cache_protect to dbblock_cache_p
# ghallmar 02/03/92 - db_directory -> db_domain
# maporter 01/12/92 - merge changes from branch 1.8.308.1
# maporter 12/21/91 - bug 76493: Add control_files parameter
# wbridge 12/03/91 - use of %c in archive format is discouraged
# ghallmar 12/02/91 - add global_names=true, db_directory=us.acme.com
# thayes 11/27/91 - Change default for cache_clone
# jloaiza 08/13/91 - merge changes from branch 1.7.100.1
# jloaiza 07/31/91 - add debug stuff
# rlim 04/29/91 - removal of char_is_varchar2
# Bridge 03/12/91 - log_allocation no longer exists
# Wijaya 02/05/91 - remove obsolete parameters
# Example INIT.ORA file
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your site. Important system parameters
# are discussed, and example settings given.
# Some parameter settings are generic to any size installation.
# For parameters that require different values in different size
# installations, three scenarios have been provided: SMALL, MEDIUM
# and LARGE. Any parameter that needs to be tuned according to
# installation size will have three settings, each one commented
# according to installation size.
# Use the following table to approximate the SGA size needed for the
# three scenarious provided in this file:
# -------Installation/Database Size------
# SMALL MEDIUM LARGE
# Block 2K 4500K 6800K 17000K
# Size 4K 5500K 8800K 21000K
# To set up a database that multiple instances will be using, place
# all instance-specific parameters in one file, and then have all
# of these files point to a master file using the IFILE command.
# This way, when you change a public
# parameter, it will automatically change on all instances. This is
# necessary, since all instances must run with the same value for many
# parameters. For example, if you choose to use private rollback segments,
# these must be specified in different files, but since all gc_*
# parameters must be the same on all instances, they should be in one file.
# INSTRUCTIONS: Edit this file and the other INIT files it calls for
# your site, either by using the values provided here or by providing
# your own. Then place an IFILE= line into each instance-specific
# INIT file that points at this file.
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
# replace DEFAULT with your database name
db_name=sales
db_files = 80 # SMALL
# db_files = 400 # MEDIUM
# db_files = 1500 # LARGE
db_file_multiblock_read_count = 8 # SMALL
# db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
db_block_buffers = 100 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
shared_pool_size = 3500000 # SMALL
# shared_pool_size = 5000000 # MEDIUM
# shared_pool_size = 9000000 # LARGE
log_checkpoint_interval = 10000
processes = 50 # SMALL
# processes = 100 # MEDIUM
# processes = 200 # LARGE
parallel_max_servers = 5 # SMALL
# parallel_max_servers = 4 x (number of CPUs) # MEDIUM
# parallel_max_servers = 4 x (number of CPUs) # LARGE
log_buffer = 32768 # SMALL
# log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
# 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 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
# # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# 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
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0starts up the instance and shuts down immediately.
Here is the log
/u01/app/oracle/oracle/product/10.2.0/db_1/bin/dbstart: Starting up database "sales"
Thu Dec 24 23:26:47 IST 2009
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Dec 24 23:26:47 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> Connected to an idle instance.
SQL> ORA-00371: not enough shared pool memory, should be atleast 62198988 bytes
SQL> Disconnected
/u01/app/oracle/oracle/product/10.2.0/db_1/bin/dbstart: Database instance "sales" warm started.
Maybe you are looking for
-
Is it possible to do this on APE or any other product?
Hello, Does anyone know whether it is possible to make something like this on Adobe Premiere Elements, or would you know what program would be best suited to create this? I've got a video already but I want to add certain images to match the stuff I
-
hello im a new bb user and i need your help , i have tried downloading animated themes from app world and they wont work , they are compatible with my phone, they dont even show up where the themes are listed , i found the ones i downloaded in my fi
-
Java.util.Properties.load() not loading all properties
Hi, I'm trying to load the following properties into my Properties class. However, Im only able to load SOME properties not ALL (11 to be precise) This is my properties file : ~~~~~~~~~~~~~~~~~~~~~ gds.host=chissd235.bankofamerica.com gds.datasource=
-
Hi I am new to jsp & java. I am slightly confused about how to go about using my database with my jsp app. Should I store all information in the database, initialize the objects everytime they are called & use them or store my objects as serialized o
-
I need to make quick reminder notes that pop up on dates I provide. How do I make iCal do just that?
I want simply to have a calendar page and to jot down a quick reminder note. I want it to pop up on dates I provide. Please tell me how to use iCal at its most basic level.