Setting init.oraparameter ASM instance Use default values sesettings. Only processes parameter may need modification. Processes parameter setting is dependent on the number of databases that connect to ASM processes= 25 + 15n, where n = # databases connected to ASM. If max processes is reache on ASM, this indicaties offten on hanging processes of cluster agents or RMAN processes
The Oracle's strategic solution for real time data integration. Oracle GoldenGate provides low-impact capture, routing, transformation, and delivery of transactional data across heterogeneous environments in real time
RACcheck is a RAC Configuration Audit tool designed to audit various important configuration settings within a Real Application Clusters (RAC), Oracle Clusterware (CRS), Automatic Storage Management (ASM) and Grid Infrastructure environment. RAC Configuration Audit Tool audits configuration settings within the following categories:
OS kernel parameters
OS packages
Many other OS configuration settings important to RAC.
CRS/Grid Infrastructure
RDBMS
ASM
Database parameters
Many other database configuration settings important to RAC.
Licensing policy for ASM Cluster File System (ACFS), now called Oracle Cloud File Systerm, is free to use in combination with any Oracle RDBMS version. De files must have a relation with the RDBMS, including non-Oracle files related to the RDBMS application. See the citation below
A restricted use license to use Oracle Cloud File System is included with all editions of the database specifically for storing Oracle Database-related configuration files, including Oracle Database software binaries and homes, Oracle Database software administrative files, and Oracle Database software diagnostic files. Customers wishing to store their own data files, or non-Oracle Database software files including data files, binaries, administrative files, and diagnostic files, in Oracle Cloud File System must separately license Oracle Cloud File System.
In the listener log file you constantly get the following warning message.
WARNING: Subscription for node down event still pending.
The warning messages are related to the Oracle TNS Listener's default subscription to the Oracle Notification Service (ONS). This subscription to ONS is introduced in Oracle 10g for RAC environment. Listener subscription to ONS is useful to use advanced features like Fast Application Notification events(FAN) , Fast Application Fail over (FAF) and Fast Connection Failover (FCN) in RAC. So in a non-RAC environment subscription to ONS is not needed. So in a standalone system we can disable it and thus avoid warning message.
Solve the WARNING message in the listener log. Disable subscription for listener to ONS. This can be done by setting the following parameter in the listener.ora.
SUBSCRIBE_FOR_NODE_DOWN_EVENT_{listener_name}=OFF
Where {listener_name} should be replaced with the actual listener name configured in the LISTENER.ORA file.
After that you need to stop and start the listener by,
lsnrctl stoplsnrctl start
Alternatively you can reload the listener if availability is important to you. Do it just by,
lsnrctl reload
This will prevent the messages from being written to the log file.
Customers often ask to what extent they can trust performance measurements and timing results of the Oracle database within a virtual machine. To fully understand the performance of applications running in a virtual machine, we can give some general guidance. See for the guideance this link Timekeeping In VirtualMachines
The following items on the ESX server is a key element that must be taken in detecting performance problems in databases that run on VMware:
Over allocation on CPU,
Resource pools, which for the next ESX cluster is planned (depending on setting, this is a ratio (shares) or a longer warranty (reservation))
CPU power management (allowing for lower CPU / clock speed for variable)
CPU affinity (linking VMs to CPUs)
The question, given the above points, is actually what is the meaning of performance measurements and numbers in a guest O / S. This applies in my view not only for VMWare, but also for other solutions.VMWare has a document that on pages 20 and 21 has explained , see the link Timekeeping In VirtualMachines
An example, what is the meaning of a statement that 360 seconds CPU is consumed as it is unclear whether the ESX cluster at that time was 100%, or CPU power management is enabled. What is the meaning of a statement that yesterday and before 360 seconds duration time was in seconds and today 720 seconds (while the number of disk and bufferreads equal). The answer depends on the last points mentioned regarding the settings of ESX.
Creating a cluster with a single pool of storage managed by Oracle ASM provides the infrastructure to manage multiple databases whether they are single instance databases or Oracle RAC databases.
With Oracle RAC databases, you can adjust the number of instances and which nodes run instances for a given database, based on workload requirements. Features such as cluster-managed services allow you to manage multiple workloads on a single database or across multiple databases. It is important to properly manage the capacity in the cluster when adding work. The processes that manage the cluster—including processes both from Oracle Clusterware and database—must be able to obtain CPU resources in a timely fashion and must be given higher priority in the system.
Oracle recommends that the number of real time Global Cache Service Processes (LMSn) on a server is less than or equal to the number of processors. (Note that this is the number of recognized CPUs that includes cores. For example, a dual-core CPU is considered to be two CPUs.).
Consolidating many small databases into a cluster, you may want to reduce the number of LMSn created by the Oracle RAC instance. By default, Oracle Database calculates the number of processes based on the number of CPUs it finds on the server. This calculation may result in more LMSn processes than is needed for the Oracle RAC instance. One LMS process may be sufficient for up to 4 CPUs.To reduce the number of LMSn processes, set the GC_SERVER_PROCESSES initialization parameter minimally to a value of 1. Add a process for every four CPUs needed by the application. In general, it is better to have few busy LMSn processes. Oracle Database calculates the number of processes when the instance is started, and you must restart the instance if you want to change the value.
Follow these steps to configure RMAN backups in Data Guard environment. When you want to managed the archivelog deletion policy from one centralpoint.
CONFIGURE ARCHIVELOG DELETION POLICY
Possible options : APPLIED ON STANDBY - enables flash recovery area to delete archivelogs that are applied on mandatory standby.
NONE - enables flash recovery area to delete archivelogs that are backed up to tertiary device and that are obsolete based on the configured backup retention policy. This is the default configuration.
CLEAR - clears the deletion policy and returns the specified configuration to default value. The default value is NONE.
Viewing the Current Deletion Policy
To view the current setting (APPLIED ON STANDBY, CLEAR, NONE) for a database, issue the following query :
SELECT NAME, VALUE FROM V$RMAN_CONFIGURATION WHERE NAME LIKE '%ARCHIVELOG DELETION POLICY%';
NAME VALUE ----------------------------- -------------- ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY
You can also find the existing configuration using the RMAN SHOW ARCHIVELOG
DELETION POLICY command:
RMAN> SHOW ARCHIVELOG DELETION POLICY
RMAN configuration parameters are: CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
When Backup is taken form the Standby Database.
Issue the following command on the primary database:
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
The following commands should be issued, after connecting to each of the other standby database servers.
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
Reconfiguring the Deletion Policy After a Role Transition
By setting this configuration on each of the other standby databases (where backups are not being taken), it will enable automatic deletion of archived logs on this standby database that have been applied to all other remote standby destinations. By default, this configuration requires that at least one remote destination is set to mandatory. Archived logs are deleted if space in the Flash Recovery Area needs to be reclaimed for new files.
Note: Mandatory standby destination can impact the primary database if the standby destination cannot be reached.
Configure RMAN standby database where backups are taken:
Issue the following command on the physical standby where the backup will be taken.
RMAN> CONFIGURE DELETION POLICY TO NONE;
Specify when the archived logs can be deleted with the CONFIGURE ARCHIVELOG DELETION POLICY COMMAND. Since the logs are backed up at the standby site, you should specified the NONE option for the log deletion policy. This will enable automatic deletion of archived logs on the standby database that are outside of the retention period or that are already backed up to tape, if additional space is needed for new backups or archived logs.
On all the other physical standby databases where backups are note taken and the primary database.
RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;
Note: That in the event of a switchover or failover, the database role changes and the appropriate CONFIGURE commands must be re-executed on new primary and standby databases.
Many ASM administrators have little or no experience with ASM mirroring, because they use External Redundancy for their diskgroups and ASM generally maintains one copy for each AU in this case. Tracking free space within a diskgroup in such a case is simple. Use the following details from view V$ASM_DISKGROUP to examine the redundancy, offline state and free space requirements for mirror recovery:
TOTAL_MB => indicates the total space in the diskgroup FREE_MB => indicates the total free space in the diskgroup REQUIRED_MIRROR_FREE_MB => indicates free space required in the diskgroup to restore redundancy by copying allocation units as described above. USABLE_FILE_MB => indicates how much of the FREE_MB may be safely used whilst leaving enough free space for mirror copy recovery in the case of disk failure TYPE => indicates the redundancy attribute of the diskgroup. OFFLINE_DISKS => indicates how many disks are offline in the diskgroup
Note: the LSDG command in the ASMCMD utility will provide the same information.
The crucial aspect of administering the diskgroups when ASM mirrors the AUs, is having enough free space to re-copy the AUs when a loss occurs. This is not a concern when external redundancy is used, but it is for normal and high redundancy, and requires that the ASM administrator be aware of the free space needs.
An "AWR Formatter" written by a friend of mine, Tyler Muth. It's pretty cool - works as a Chrome plugin - and it makes an AWR report a little more 'friendly' to use. It creates hot links for many of the wait events (so you know what they mean) and it summarizes up a lot of stuff - making the AWR report a lot more "interactive". Check it out and give him feedback on it if you have time.
Customize your Firefox to use acronym and contents of mentioned Metalink Note displayed without the need to open Metalink web site. “mn 1269139.1″ (mn was an acronym for Metalink Note)
The Problem Enterprise Manager Database Control with Oracle Database 10.2.0.4 and 10.2.0.5 " The DBCONSOLE" will not work. The root certificate used to secure communications via the Secure Socket Layer (SSL) protocol will expire on 31-Dec-2010 00:00:00.
ATTENTION - Enterprise Manager Database Control 10.2.0.4 Or 10.2.0.5 - Patch Required from 31-Dec-2010 onwards [ID 1217493.1]
Solving this problem If you plan to configure Database Control with either of these Oracle Database releases, Oracle strongly recommends that you applyPatch 8350262to your Oracle Home installations before you configure Database Control. Configuration of Database Control is typically done when you create or upgrade Oracle Database, or if you run Enterprise Manager Configuration Assistant (EMCA) in standalone mode.
After upgrading to the 10.2.0.5.0 release the database is encounter a file handle leak. The leak is seen in production and development instances. The leak happens on different processes (emagent and MMNL process are the current ones).
Test on growing of openfiles:
lsof -p 10140 |wc -l => 600
lsof -p 10140 |wc -l => 759
Now we wait for the sollution of oracle to solve this bug.
The max file limit has been reached so the db will have to be shutdown or the
process killed, if possible, to free up files.The leak happen over time and manifests itself when the limits are reached as error ORA-27041.
The sollotion VARIOUS ORACLE PROCESSES CONSUMING LARGE QUANTITIES OF FILE DESCIPTORS (NFILES) Patch 9981011. For us we need the Patch download for Oracle 10.2.0.5 on HP-UX Itanium.
This patch is also suitable for a 10.2.0.5.1 home, there are no conflicts with 10.2.0.5.1
Is it possible to do a RMAN backup of the Flash Recovery Area (FRA) to disk. The standard method by RMAN is that this is only possible with the use of a SBT channel/library. The RMAN command 'BACKUP RECOVERY AREA' works only with SBT channels, meaning a tertiary storage such as tape.
Oracle has introduce an emulator for SBT library to do a backup of the FRA to disk. The RMAN disksbt library, which emulates a SBT library (but it writes the backups to a disk location). This disksbt, can be used to test backup the FRA to a disk location
For Example:
RMAN> run { allocate channel dev1 type sbt parms='SBT_LIBRARY=oracle.disksbt, ENV=(BACKUP_DIR=/home/oracle)'; crosscheck backup device type sbt_tape; delete noprompt expired backup; }
In patch set 11.2.0.2 a new behaviour for datafile write errors has been implemented.With this release ANY write error to a datafile will cause the instance to abort.
Before 11.2.0.2 those errors usually led to an offline datafile if the database operates in archivelog mode (your production database do, don’t they?!) and the datafile does not belong to the SYSTEM tablespace. Internal discussion found this behaviour not up-to-date and alligned with RAC systems and modern storages. Therefore it has been changed and a new underscore parameter got introduced.
_DATAFILE_WRITE_ERRORS_CRASH_INSTANCE=TRUE
This is the default setting´and the new behaviour beginning with Oracle 11.2.0.2
If you would like to revert to the pre-11.2.0.2 behaviour you’ll have to set in your init.ora/spfile this parameter to false. But keep in mind that there’s a reason why this has been changed. More info in MOSC Note: 7691270.8
New Behaviour for Automatic Mamory Management (AMM):
Unfortunately a “new feature” in 11gR2 turns AMM on unless a hidden parameter called _memory_imm_mode_without_autosga is set to FALSE.
This means if you have disabled AMM , upgrades to 11gR2, you can find that AMM has reappeared, even if you think that you have disabled it. [Oracle11gR2 AMM restart]
There is a MOSC note about AMM in 11gR2 that notes that this regression back to AMM is the expected behavior in 11.2 for immediate memory allocation requests and that Oracle added this behavior as a 11gR2 new feature when automatic memory management was disabled.
More info MOSC Note:1269139.1, “SGA Re-Sizes Occurring Despite AMM/ASMM Being Disabled(MEMORY_TARGET/SGA_TARGET=0)”
Regarding to the scan listener is the relocation not being handled correctly by Oracle Enterprise Manager(OEM) 11gR1 (shows target as down after relocate!), Oracle has solved this by the following bugs/fixes:
Apply Patch 10118817 on OMS: BUG 10118817 - SCAN LISTENERS NOT BEING DISPLAYED CORRECTLY IN GC CONSOLE AFTER FAILOVER (this is a generic platform fix)
Apply Patch 10392806 on AGENT: Bug 10392806: METADATA CHANGES FOR BUG 10118817 (this patch is available on linux x86/x86-64)
Usually after these patches, the fix should work, if all the post install steps, agent patches are applied correctly. There is one more scenario in the bug 10118817 where in the cluster target metrics in EM "crs_event" and "resource_status" are present in $AGENT_HOME/<host>/sysman/emd/collection/cluster_<ClusterName>.xml. You will have to remove these metrics, as mentioned in the bug.
Keep in mind those patches are conflicing with the PSU 2 patch. There is a request by Oracle to solve this also for the PSU patch 2.If installed the PSU 2 patch you can not use this patch .
Oracle Locator Express is a replacement tool for the standard Oracle Home Selector. It sits in the system tray and allows you to easily switch between multiple Oracle Homes with just one click.
Oracle Locator Express is also compatible with Oracle Instant client. What's new in this version: Version 2.0.1 fixes a bug where the version of the Oracle client was displayed incorrectly for a 11gr2 client
First, download the latest copy of the dbwsclient.jar file:
Pre 10g: dbws-callout-utility.zip (10.1.2) 10g: dbws-callout-utility-10R2.zip (10.1.3.0) 10g & 11g latest: dbws-callout-utility-10131.zip (10.1.3.1) Extract the jar file from the zip file into the $ORACLE_HOME/sqlj/lib directory.
The jar file can be loaded into the SYS schema for everyone to access, or into an individual schema that needs access to the web client.
# Load into the SYS schema.
export PATH=/u01/app/oracle/product/10.2.0/db_1/bin:$PATH cd /u01/app/oracle/product/10.2.0/db_1/sqlj/lib
SELECT get_joke FROM dual; -- # Test webservice address http://interpressfact.net/webservices/getjoke.asmx -- on 11g issue with ACL /* -- Issue with ACL used sys then no issue with acl DBMS_NETWORK_ACL_ADMIN DBMS_NETWORK_ACL_UTILITY ERROR at line 1: ORA-29532: Java call terminated by uncaught Java exception: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: HTTPClient.AuthSchemeNotImplException: NTLM ORA-06512: at "DBAPRD4.UTL_DBWS", line 404 ORA-06512: at "DBAPRD4.UTL_DBWS", line 401 ORA-06512: at "DBAPRD4.GET_JOKE", line 25 */
Solving the security issue in Oracle by setting up an ACL or use the user sys to execute the function.
BEGIN DBMS_NETWORK_ACL_ADMIN.create_acl ( acl => 'test_acl_file.xml', description => 'A test of the ACL functionality', principal => 'DBAPRD4', is_grant => FALSE, privilege => 'connect', start_date => SYSTIMESTAMP, end_date => NULL); COMMIT; END; / BEGIN DBMS_NETWORK_ACL_ADMIN.assign_acl ( acl => 'test_acl_file.xml', host => '*', lower_port => NULL, upper_port => NULL); COMMIT; END; / BEGIN DBMS_NETWORK_ACL_ADMIN.unassign_acl ( acl => 'test_acl_file.xml', host => '192.168.2.3', lower_port => 80, upper_port => NULL); COMMIT; END; /
SELECT dbaprd4.get_shakespeare('To be, or not to be') FROM dual; SELECT dbaprd4.get_shakespeare('O Romeo, Romeo! wherefore art thou Romeo') FROM dual; SELECT dbaprd4.get_shakespeare('Let's kill all the lawyers') FROM dual; SELECT dbaprd4.get_shakespeare('Good night sweet prince') FROM dual;
Great Oracle ACFS is now supported by HP Dataprotector. See the Platform and integration support matrix link in this blog
Question
Is it possible to backup Oracle ACFS with HP DATAPROTECTOR. Currently we can't see the mount point that we have created on the system with the HP DATAPROTECTOR GUI. We used Data Protector 6.11 [dd - Jan 12,2011]
Answer from HP Support
It is Supported with Data Protector 6.11 patches: PHSS_41457 / PHSS_41458 / DPLNX_00136 / DPSOL_00430.
Is it possible to use a central tnsnames.ora on a shared file systems insite a Real Application Server. The answer to the question is YES. If the centralized tnsnames.ora is not correctly setup, it will produce the following errors [PRKP-1001 and CRS-0215 errors] at startup of the database or instance with SRVCTL. When using SQLPLUS to startup the database instance everything works as designed. Why SRVCTL is not working correctly is that, the TNS_ADMIN is not register into the Oracle Cluster Registry for the current database and instances.
The following steps in this blog will explain to you how you can solved the [PRKP-1001 and CRS-0215 errors] at startup of a database or instances by using SRVCTL statement with a centralized tnsnames.ora.
The first step is adding the TNS_ADMIN environment to the user profile where you have placed the tnsnames.ora file. This environment setting will be used by sqlplus.
export TNS_ADMIN=/oravar/oracle/admin
The TNS_ADMIN environment setting seems not be used by "SRVCTL start -d" statement. Using SRVCTL commando to startup the database or instances will result into an error.
srvctl start database -d JOORDS PRKP-1001 : Error starting instance JOORDS1 on node joords_1 CRS-0215: Could not start resource 'ora.JOORDS.JOORDS1.inst'. PRKP-1001 : Error starting instance JOORDS2 on node joords_2 CRS-0215: Could not start resource 'ora.JOORDS.JOORDS2.inst'.
What is now the problem that SRVCTL is not using the TNS_ADMIN environment that we have set into the user profile. Looking into the following logfile "$ORACLE_HOME/log/joords_rac1/racg/imon_JOORDS.log" we see the following information related to the error.
SQL> ORA-00119: invalid specification for system parameter LOCAL_LISTENER 2011-01-17 12:13:00.131: [ RACG][1221908800] [20265][1221908800][ora.JOORDS.JOORDS1.inst]: ORA-00132: syntax error or unresolved network name 'LISTENER_JOORDS_1' ORA-01078: failure in processing system parameters SQL> Disconnected
It seems that the system parameter LOCAL_LISTENER can not be solved, and results in a startup failure of the database or instances.
What is causing this problem. SRVCTL works from the Oracle Cluster Registry information and does not know the TNS_ADMIN environment setting for the database and instances. Solving this problem is adding the TNS_NAMES environment setting to the Oracle Cluster Registry for the database and instances. The SRVCTL setenv statements to add the attribute TNS_ADMIN to the Oracle Cluster Rergistry have only to be executed from one node only.
View Channel
