SPARC is a popular Sun Solaris architecture. Many Oracle products are based on Java and hence require JDK (Java Development Kit) to be installed to support them. Here is the procedure on installing 64 bit JDK in Solaris SPARC
1) Download JDK from the sun website
2) Copy the downloaded files to /tmp. Connect to server from local desktop by using telnet, FTP and such clients. Transfer file to /tmp
3) Create a new directory and change to that location
In place of version it should be numerical values like 1.5 etc
4) Install JDK from /tmp
5) Check for successful JDK installation
./java -d64 -version
Undo Management is the way in which undo segments are managed in the Oracle database. Undo segments are previously called rollback segments. In Oracle database 11g get to know the management mode using the following query.
SQL> show parameter undo_management
NAME TYPE VALUE
———————————— ———– ——————————
undo_management string AUTO
SQL> select value from v$parameter where name=’undo_management’;
The parameter used is undo_management. The value is auto which means automatic undo management is the default management mode. If it returns value manual we can change it to auto mode using ALTER SYSTEM command.
Oracle emca (Enterprise Manager Configuration Assistant) Command Line Interface allows us to configure the enterprise manager environment.
operation – operation to be performed. Possible values are help/h, config, deconfig, displayconfig, Addinst,deleteinst,reconfig,upgrade,restore
mode – mode of the command. Possible values are dbcontrol,centralAgent,all.ports
flags – flags of the command. Possible values are db,asm,db_asm,repos create, repos drop, cluster, silent,backup
parameters – Parameters to be used. Possible values are General parameters, backup parameters, ASM parameters, cluster parameters.
General Parameters can be – respfile,sid,port,oracle_home,listener_oh,email_address,mail_server_name,dbsnmp_pwd,sysman_pwd,sys_pwd,src_oh
Backup Parameters – HOST_USER,HOST_USER_PWD,BACKUP_SCHEDULE
ASM parameters – ASM_OH,ASM_SID,ASM_PORT,ASM_USER_ROLE,ASM_USER_NAME,ASM_USER_PWD
Cluster/Clustered Database Parameters – cluster_name,db_unique_name,em_node,em_sid_list,service_name
Oracle Dataguard 11g – Important V$ Views have been discussed here :
v$Managed_STANDBY – Provides status information on physical standby database background processes. We can obtain activities performed by different processes using this view
v$DATAGUARD_STATS – Provides information about redo data including redo data generated by the primary database that is not yet available on the standby database. This shows redo data that has not yet been applied to standby database. This provides information on data loss in case of primary database crash
V$STANDBY_APPLY_SNAPSHOT – Provides information on current redo apply rate in KB/sec
V$RECOVERY_PROGRESS – Used to monitor efficient recovery operations. It is used to estimate time required to complete the current operations in progress
I tried performing tablespace point in time recovery popularly called as TSPITR today using oracle RMAN (recovery manager) in Oracle database 11g. I tried issuing command without until time ‘timestamp’ and found the following error
RMAN> recover tablespace pointintime auxiliary destination ‘C:appusernameoradataauxdata’;
Starting recover at 10-MAY-10
using channel ORA_DISK_1
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of recover command at 05/10/2010 16:48:31
RMAN-05020: cannot specify AUXILIARY DESTINATION option for normal recovery
This is an error in syntax. It needs to be UNTIL TIME ‘timestamp’
RMAN> recover tablespace pitr until time ’10-05-10 16:35:00′ auxiliary destination ‘C:appusernameoradataauxdata’;
This will fix the issue.
The emctl utility is used to configure agents and consoles for not only the Grid Control, but also for the Database Control and Oracle application server.We can check the status of the agent and stop and start the agent service with the following commands:
emctl status agent – To get the current status of agent. (e.g. agent is running and ready)
emctl start agent – To start an agent
emctl stop agent – To stop an agent
The emctl executable is common to both Unix/Linux and Windows systems.
There is a seperate emctl executable for the Database Control and the Management Agent.
We can find appropriate executable by using full path for it,under right home directory. If we just type emctl we may be looking at the wrong executable
By enabling block-change tracking RMAN knows which blocks have been changed by using a change-tracking file.There is slight overhead in space usage and maintenance of the tracking file every time a block is changed, it is worth using it if frequent incremental backups are performed on the database
SQL> alter database enable block change tracking using file ‘location’;
File by name ctf.xxxx is created
We can use the view v$block_change_tracking to check the status (ENABLED/DISABLED)