Solution :
Just change from SID to SERVICE_NAME (Thanks to my colleague for his past experience).
examples:
I changed from
(SID = cwsapp_dev) to (SERVICE_NAME = cwsapp_dev) ..thats it.

–Manzoor A.Mirza.

Error:  javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated for RAC on HPUX.  (Its a bug in Grid Control agent Installer..)

Cause:During the installation of Agent software we entered wrong password for Grid repository Database (Management server for sysman). Expected behavior,  installer should complain for wrong password, but its take that password and complain after all the installation completed as mention error.
Solution :
step 1    :     first check whether agent is secure or unsecure.
# emctl secure(or unsecure) agent;
#emctl secure agent [registration password];
– When you try to secure agent as mention above
It will ask for sysman password (Please enter correct password here..).

Step 2    :    Open Oracle Enterprise Manager (Grid Control) > select Databases tab
> select Name of the effected Database name  > click on Configure > follow  the                      steps as guided by GUI. (Note: GUI ask for DBSNMP password during configuration.)  Wait for few minutes Grid discovered your DB again..

–Thanks and Regards

Manzoor A. Mirza.

Don’t compare yourself with any one in this world. If you compare, you are insulting yourself.
Don’t complain about others; change yourself if you want peace.
It is easier to protect your feet with slippers than to cover the earth with carpet.
No one can go back and change a bad beginning, but anyone can start now and create a successful ending.
Easy is to judge the mistakes of others. Difficult is to recognize our own mistakes.
If a problem can be solved, no need to worry about it. If a problem cannot be solved what is the use of worrying?
“Changing The Face” can change nothing. But “Facing the Change” Can change everything.
Be bold when you loose and be calm when you win.
No one will manufacture a lock without a key. Similarly ALLAH won’t give problems without solutions.
Every successful person has a painful story. Every painful story has a successful ending. Accept the pain and get ready for success.
Heated gold becomes ornament. Beaten copper becomes wires. So the more pain your get in life you become more valuable.
Mistakes are painful when they happen. But year’s later collection of mistakes is called experience, which leads to success.
Life laughs at you when you are unhappy.
Life smiles at you when you are happy.
Life salutes you when you make others happy.
If you miss an opportunity don’t fill the eyes with tears. It will hide another better opportunity in front of you.

–Manzoor A.Mirza

some time it was really necessary  to terminate  a expdb/impdp jobs because of any valid reason which impact database.

here are the steps for quick references, how can we terminate the expdp/impdp job,which you really wants to terminate.

step 1:  take the job_name from below views
select * from USER_DATAPUMP_JOBS;
select * from DBA_DATAPUMP_SESSIONS;

step 2: try to attach to that job_name which you find out in step1.

oracle@aa: /u02/backups # impdp system/***** attach=test_DUMP11(job_name)

step 3:  stop job immediate

impdp> STOP_JOB=IMMEDIATE
impdp>kill_job

–Manzoor A.Mirza.

In Oracle/PLSQL, the instr function returns the location of a substring in a string.

The syntax for the instr Oracle function is:

Issue : when we try to install client on HP-UX machine where a database is already installed. Installer try to check for oraInventory file to overwrite its registry, which is not accepted.

Solution : we need to create separate oracleInst. inventory file as metnion below for client.

step 1: create the new file oraInst.loc under <client_home_location>/oraInventory,     which contain
bobject@ebizwily: <client_home_location>/oraInventory # more oraInst.loc

inventory_loc=<client_home_location>/oraInventory
inst_group=users

step 2: execute the installer by assigning the path as below

./runInstaller -invPtrLoc <client_home_location>/oraInventory/oraInst.loc ORACLE_HOSTNAME=ebizwily

–Manzoor A.Mirza

solution:

We need to check and update the IPs or Hostname or port for specific down listener, and restart to it.

–what is Oracle Text:

Oracle Text enables text queries through SQL and PL/SQL from most Oracle interfaces. By installing Oracle Text with an Oracle Database server, client tools such as SQL*Plus, Oracle Forms, and Pro*C/C++ are able to retrieve and manipulate text in Oracle Database.

Oracle Text manages textual data in concert with traditional data types in Oracle Database. When text is inserted, updated, or deleted, Oracle Text automatically manages the change.

Configure ORACLE TEXT using GUI(dbca)
————————————-

OPEN Xmanager window
> open terminal >>check for xclock >
(set oracle_sid where you want to work );
>run dbca utility >
>then follow GUI utility and select Oracle text.>

FYI..

Configuring Oracle Text Using Command-Line Tools
————————————————

–Manually configuring Oracle Database for use with Oracle Text consists of creating a tablespace for Oracle Text data dictionary tables and then creating username ctxsys and Oracle Text data dictionary tables.
1.Start SQL*Plus:
oracle@eippd : sqlplus /NOLOG

2.Connect to Oracle Database with account SYSDBA:
SQL: CONNECT / AS SYSDBA

3.Create a tablespace for Oracle Text data dictionary tables:
SQL> CREATE TABLESPACE tablespace_name DATAFILE ‘ORACLE_BASE\oradata\db_name\drsys01.dbf’ SIZE 80m;

4.Connect AS SYSDBA:
SQL> CONNECT USERNAME/PASSWORD AS SYSDBA

5.Run script dr0csys.sql to create username ctxsys:
SQL> @ORACLE_BASE\ORACLE_HOME\ctx\admin \dr0csys.sql password default_tablespace_name temporary_tablespace_name;

where:
*password is the password that you intend to use for username ctxsys.
* default_tablespace_name is the default tablespace for Oracle Text data dictionary tables. Set the default tablespace to the value of tablespace_name in step 3.
*temporary_tablespace_name is the temporary tablespace for Oracle Text data dictionary tables. Set the temporary tablespace to the value of tablespace_name in step 3.
6.Connect as ctxsys:
SQL> CONNECT ctxsys/password
7. Run script dr0inst.sql to create and populate Oracle Text data dictionary tables:
SQL> @ORACLE_BASE\ORACLE_HOME\bin\dr0inst.sql;

8.Run the language-specific default script, where xx is the language code (for example, us):
SQL> @ORACLE_BASE\ORACLE_HOME\ctx\admin\defaults\drdefxx.sql;

9.Exit SQL*Plus:
SQL> EXIT

–Manzoor A.Mirza

I put FGA audit to know which tables are not used by application or developers from very long time. Here below are the steps:

–create unused_table and  a policy over this table.

create table unused_tables
as select object_name from dba_objects
where owner =’APP_USER’
and object_type=’TABLE’
and object_name not in ( select table_name from sys.dba_tab_modifications where table_owner=’APP_USER’);

– create policy on all unused table.

select ‘exec dbms_fga.add_policy(object_schema => ”APP_USER”, object_name => ”’ || object_name || ”’, policy_name => ”’ || object_name || ‘_P”);’
from unused_tables;

NOTE:With the above policy, only select statement can be audited if we required more DMLs auditing then  need to add condition to policy.

examples:

exec dbms_fga.add_policy(object_schema => ‘APP_USER’, object_name => ‘ACC_PAYSLIP_NEW’, policy_name => ‘ACC_PAYSLIP_NEW_P’);

exec dbms_fga.add_policy(
object_schema=>’UWCLASS’,
object_name=> ‘FGA_DEMO’,
policy_name=> ‘UW Audit’,
audit_condition=> ‘status = ”A”’,
audit_column=> ‘last_name, salary’,
handler_schema => ‘UWCLASS’,
handler_module=> ‘FGA_HANDLER’,
enable => TRUE,
statement_types => ‘INSERT, UPDATE’
audit_trail => DBMS_FGA.DB+EXTENDED,
audit_column_opts => dbms_fga.all_columns);

–dropping the policy from all unused _table.

select ‘exec dbms_fga.drop_policy(object_schema => ”APP_USER”, object_name => ”’ || object_name || ”’, policy_name => ”’ || object_name || ‘_P”);’
from unused_tables;

–syntax for enable and disable of policy –take below select statements and execute.

select ‘begin dbms_fga.disable_policy(object_schema => ”APP_USER”, object_name => ”’ || object_name || ”’, policy_name => ”’ || policy_name ||”’);end; /’
from dba_fga_audit_trail where db_user not in (‘DBA_USER’);

–important VIEWS related to FGA.

select count(*)  from sys.fga_log$ where dbuid not in (‘USER1′,’USER2′);
select dbuid, count(*)  from sys.fga_log$  group by dbuid  where dbuid  not in (‘USER1′,’USER2′);
select * from dba_audit_policies;
select * from dba_audit_policies  where  enabled=’NO’;
select * from dba_audit_policies  where  enabled=’YES’;
select * from dba_fga_audit_trail where db_user not in (‘USER1′,’USER2′);
select distinct object_name, policy_name from dba_fga_audit_trail where db_user not in (‘USER1′,’USER2′);
SELECT  policy_name, object_name, statement_type, os_user, db_user FROM dba_fga_audit_trail;
select * from dba_fga_audit_trail where db_user not in (‘USER1′,’USER2′);

NOTE :USER1 and USER2 are generally DBA users.

–Manzoor A.Mirza

virtual private databases, or VPD, which as also known as fine-grained access control(FGAC). It is also commonly known as Row Level Security .

step 1 : create a function which return true or false.

/*function which return true or false , here always return false*/

CREATE OR REPLACE
FUNCTION vpd_col_mask (obj_owner IN VARCHAR2, obj_name IN VARCHAR2)
RETURN VARCHAR2
AS
BEGIN
RETURN ‘rowid = ”0”’;
END vpd_col_mask;
/

step 2:
/*DBMS that add the policy for specific user’s object coluumns */

BEGIN
DBMS_RLS.ADD_POLICY(object_schema=>’YYYY’,
object_name=>’PS_EXTRA_INFO’,
policy_name=>’PS_EXTRA_INFO_policy’,
function_schema=>’SYSTEM’,
policy_function=>’vpd_col_mask’,
sec_relevant_cols=>’COL_NAME’,
policy_type => DBMS_RLS.SHARED_STATIC,
sec_relevant_cols_opt=>dbms_rls.ALL_ROWS);
END;
/

/* dbms for dropping policy */

begin
dbms_rls.drop_policy(object_schema => ‘YYYY’,
object_name => ‘PS_EXTRA_INFO’,
policy_name=>’PS_EXTRA_INFO_policy’);
end;
/

/* grant and revoke the policy to/from individuals*/

grant EXEMPT ACCESS POLICY to username;
revoke EXEMPT ACCESS POLICY from username;

important VIEWS related to VPD:

select * from user_policies;
select * from dba_policies;
select * from v$vpd_policy;
select * from DBA_POLICY_CONTEXTS;
select * from eip.STC_PS_EXTRA_INFO

–Manzoor A.Mirza

when we try to add disks to ASM we found that ‘/dev/rdsk/c2t1d0′ , ‘/dev/rdsk/c2t1d1′ and ‘/dev/rdsk/c2t1d1′ etc doesnot have entry in init+ASM1.ora file. so we try to add that new entry in init+ASM1.ora file.

updating asm_diskstring parameter for new entry on node1 using dbca ,ignoring other node(Its a mistake). As soon we update the parameter on node1, other node2 went down because of difference in init file-thanks for RAC which prevent us from down time.
we can see new disks entry on node1.

solution :
——–

As we can see new disks entry on node1.
(that need to be drop manully so as to be consistent on both nodes, mount conflicting diskgroup and then bounced ASM instance – which is to be save side.)

(Astonishing part for me: dbca update init+ASM1.ora file also, leaving other node init+ASM2 file same as old).
FYI to note..
disks permission :
If direct path have permission (oracle:oinstal) then alternative path must have(bin:sys) or viceversa.  be carefull….

correct way for adding entry in init+ASM1.ora file.

since asm_diskstring parameter is dynamic, execute below statement on all the nodes one by one.

SQL>alter system set asm_diskstring =’/dev/rdsk/c6*’,'/dev/rdsk/c2t1*’,'/dev/rdsk/c9*’,'/dev/rdsk/c3*’

FYI,ASM don’t have spfile, it points to pfile.
location : init+ASM1.ora -> /u01/app/oracle/product/10gr2/admin/+ASM/pfile/init.ora.

then, update manually init+ASM1.ora file to keep ready for future bounce DB to take its new effects.Otherwise when you bounce DB, it read from old init+ASM1.ora file (reads old values) and complain.

–Manzoor A.Mirza.