Thursday, May 28, 2009

Data Guard Installation (Step 2)

PART 2

Primary Database:
Make the corresponding changes:

*.db_unique_name=’test’
*.LOG_ARCHIVE_CONFIG=’DG_CONFIG=(test,teststb)’
*.LOG_ARCHIVE_DEST_1=’location=C:\oracle\archive arch
mandatoryvalid_for=(ONLINE_LOGFILES,ALL_ROLES)
db_unique_name=test’
*.LOG_ARCHIVE_DEST_2=’service=teststby lgwr sync
affirm net_timeout=30valid_for=(ONLINE_LOGFILES,ALL_ROLES) db_unique_name=teststby’
*.log_archive_dest_state_1=’ENABLE’
*.log_archive_dest_state_2=’ENABLE’
*.fal_server=teststby
*.fal_client=test
*.db_file_name_convert=’C:\oracle\product\10.2.0\oradata\teststby’,‘C:\oracle\product\10.2.0\oradata\test’
*.log_file_name_convert=’C:\oracle\product\10.2.0\oradata\teststby’,‘C:\oracle\product\10.2.0\oradata\test’

Sunday, May 24, 2009

Data Guard Installation (Step 1)

PART 1

This focuses on setting up a test environment on a single node.
The DBA can adapt this to set up a production environment.
By Rizwan Shafiq

Step 1:
Install an Oracle database and validate it is in Archive log Mode.
If Archive log is disabled enable it before continuing.
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination C:\oracle\product\10.2.0\archive
Oldest online log sequence 66
Next log sequence to archive 68
Current log sequence 68
Step 2:
Enable force logging mode.
SQL> alter database force logging;
Database altered.
Step 3:
Identify all the datafiles to copy for a cold back up or do
an RMAN backup.Since this is test environment I will shutdown
the database and do a cold backup.
SQL> select name from v$datafile;
NAME
———————————————————————-
C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\SYSTEM01.DBF
C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\UNDOTBS01.DBF
C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\SYSAUX01.DBF
C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\USERS01.DBF
C:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\EXAMPLE01.DBF

SQL>
Step 4:
In a windows environment create the service for the standby database.
You will also have to create the folders and environment for the
standby database.
C:\>oradim -new -sid stby -intpwd teststby -startmode manual
C:\oracle\product\10.2.0\oradata\teststby – Create this folder
C:\oracle\product\10.2.0\admin\teststby – Create this folder and
all the folders underneath. Like bdump, udump, etc. Or just copy
the production one.
Note: Since this is a dataguard environment on a single test node
I do not have to install all the Oracle software again.
Step 5:
Shutdown Primary database and move the datafiles
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
Move the datafiles from step 3 into the oradata standby environment.
C:\oracle\product\10.2.0\oradata\test
C:\oracle\product\10.2.0\oradata\teststby
Step 6:
Create a standby control file and start the database
SQL> startup mount;
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS
‘ C:\oracle\product\10.2.0\oradata\teststby\teststby.ctl’;
Database altered.
SQL> alter database open;

Step 7: Create the Primary and Standby init.ora/spfile to
facilitate Dataguard.

SQL> CREATE PFILE= ‘C:\oracle\product\10.2.0\testinit.ora’
from spfile;
File created.

Primary Database:

free counters

Tuesday, May 19, 2009

Oracle Apps 11i Tutorials : Implementing Key Flex field and Descriptive Flex field


This tutorial tells you about implementation and other features provided in the implementation section .

Sponsored Links

Implementing Flex fields
Key Flexfield
The basic steps in defining a key Flexfields are as given below. You may or may not use all the steps. The detailed explanation is being followed after the steps.

Identifying Key flexfields that are required for you Oracle Applications installation
Designing a Key flexfield structure
Selecting the appropriate Key flexfield to define
Defining structure information for the Key flexfield
Defining segment attributes
Defining flexfield qualifiers
Defining segment qualifiers
Implementing optional features as needed
To define the key Flexfield structure, you need to open the Key Flexfield segment form as shown in the figure 5 below. The navigation path is Application Developer à Flexfield: Key à Segments.

Wednesday, May 13, 2009

Oracle E Books

Advanced SQL Functions in Oracle 10g
Designed to exploit Oracle 10g's SQL, this book is a comprehensive look at Oracle 10g's analytical functions, MODEL statements, and regular expressions...

http://www.flazx.com/ebook4395.php

Beginning Oracle Database 11g Administration: From Novice to Professional (Beginning from Novice to Professional)
This book, written by veteran Oracle database administrator Iggy Fernandez, a regular on the Oracle conference circuit and the editor of NoCOUG Journal, is a manageable introduction to key Oracle database administration topics including planning, installation, monitoring, troubleshooting, maintenance, and backups, to name just a few. As is clear from the table of contents, this book is not simply a recitation of Oracle Database features such as what you find in the reference guides available for free download on the Oracle web site. For example, the chapter on database monitoring explains how to monitor database availability, database changes, database security, database backups, database growth, database workload, database performance, and database capacity.


http://www.flazx.com/ebook12675.php

Monday, May 4, 2009

Special Triggers in the Template Form in Oracle Apps 11i

Oracle Apps 11i : Special Triggers in the Template Form in Oracle Apps 11i
This document provides an overview of the Special Triggers in the Template Form. The template form contains many form level triggers. These triggers are required for the proper operation of other routines. They are also aid in making the form respond to and behave properly in case of standard events. These triggers must not be deleted or to ensure the proper functioning of the form. Also, code can be added to these triggers but, the existing text must not be deleted.

These triggers are listed below:

KEY–CLRFRM
KEY–COMMIT
KEY–DUPREC
KEY–EDIT
KEY–EXIT
KEY–HELP
KEY–LISTVAL
KEY–MENU
ON–ERROR
POST–FORM
PRE–FORM
WHEN–FORM–NAVIGATE (reference)
WHEN–NEW–BLOCK–INSTANCE
WHEN–NEW–FORM–INSTANCE
WHEN–NEW–ITEM–INSTANCE
WHEN–NEW–RECORD–INSTANCE
WHEN–WINDOW–CLOSED
WHEN–WINDOW–RESIZED
User–Named Triggers:
ACCEPT
CLOSE_THIS_WINDOW (reference)
CLOSE_WINDOW
EXPORT (referenced)
FOLDER_ACTION
FOLDER_RETURN_ACTION
LASTRECORD (reference)
MENU_TO_APPCORE (reference)
QUERY_FIND
STANDARD_ATTACHMENTS (reference)
ZOOM (reference)
You cannot change triggers that are referenced into the form.

Triggers That Often Require Some Modification
ACCEPT: This trigger is executed when ‘Action, Save and Proceed’ menu choice is invoked. It saves and moves to the next record of the block specified as the First Navigation Block.

KEY–DUPREC: This trigger disables the default duplicate record functionality of Oracle Forms.

KEY–CLRFRM: This trigger validates the record before attempting to clear the form.

KEY–LISTVAL: This trigger is invoked when the LOV is invoked / in case of flexfield operations.

ON–ERROR: This trigger is executed when an error occurs and it processes all errors, server or client side, using Message Dictionary calls.

WHEN–NEW–FORM–INSTANCE: This trigger as executed when a new form is opened.

WHEN–NEW–RECORD–INSTANCE: This trigger is executed when the cursor navigates to a new record.

WHEN–NEW–BLOCK–INSTANCE: This trigger is executed when the cursor navigates to a new block.

WHEN–NEW–ITEM–INSTANCE: This trigger is executed when the cursor navigates to a new field.


Triggers That Cannot Be Modified



Oracle Applications does not support the modification of the following form–level triggers in any way.



CLOSE_THIS_WINDOW: This trigger invokes APP_CUSTOM.CLOSE_WINDOW from the menu Action–>Close Window.

CLOSE_WINDOW: This trigger processes all window close events. Code that processes the close window events must reside in the APP_CUSTOM.CLOSE_WINDOW package.

EXPORT: This trigger processes invocation of the”Action, Export” menu choice.

FOLDER_ACTION: This trigger processes invocation of entries on the Folder menu.

EXPORT: This trigger processes invocation of the”Action, Export” menu choice.

FOLDER_ACTION: This trigger processes invocation of entries on the Folder menu.

KEY–COMMIT: This trigger processes commits in normal or called forms.

KEY–EDIT: This trigger performs flexfield operations, or Calendar or Editor Invocation.

KEY–EXIT: This trigger processes Close events, and leaves enter–query mode.

KEY–HELP: This trigger invokes the Window Help system.

LASTRECORD: This trigger processes the menu event Go–>Last Record.

MENU_TO_APPCORE: This trigger supports the Special menu.

STANDARD_ATTACHMENTS: This trigger processes invocation of the Attachments menu entry or toolbar button.

WHEN–WINDOW–CLOSED: This trigger centralizes window close events from the Oracle Applications or Window Manager menu.