WARNING FOR ORACLE STANDARD DATABASE USERS,
10G TUNING FEATURES RESTRICTIONS!!!!

Hi,
If you are Oracle Standard Database user, you had heard about new tunning features like access and Sql Access advisors.
Now you must know you can't use them.

To use this packs you must have a separate license AND you MUST be using Oracle Enterprise Edition.

1) If you are using Database Control, the first time you connect using SYSMAN, you must disable that features.
2) You must be aware you can use these packages too from the Database
The usage of this features is registered in the database
For example:
Views
V$ACTIVE_SESSION_HISTORY
DBA_HIST_*
DBA_ADVISOR_*
MGMT$*
packages
DBMS_SQLTUNE,DBMS_ADVISOR,DBMS_WORKLOAD_REPOSITORY
Scripts
awrrpt.sql, awrrpti.sql, addmrtp.sql, addmrpti.sql,
awrrpt.sql, awrrpti.sql, addmrpt.sql, addmrpti.sql, ashrpt.sql, ashrpti.sql,
awrddrpt.sql, awrddrpi.sql, awrsqrpi.sql, awrsqrpt.sql, sqltrpt.sql.
Other Database Control features
Oracle Configuration Management Pack
¦ Database and Host Configuration
¦ Deployments
¦ Search configuration
¦ Compare configuration
¦ Policies, including Security checks and scoring

The detailed information is in online documentation
http://www.oracle.com/pls/db102/portal.portal_db?selected=3

Oracle® Database Licensing Information
10g Release 2 (10.2)
B14199-03
http://www.oracle.com/pls/db102/to_pdf?pathname=license.102%2Fb14199.pdf&remark=portal+%28Books%29  ¶ 6:13 AM 0 comments

  Solving definetively the mutation error on triggers ORA-04091: table X is mutating

I had several times this error, to get the creation of a historic table of modifications.
This problem is simply solved adding three lines

PRAGMA AUTONOMOUS_TRANSACTION; <-- You have to add this 1/3
COMMIT; <-- You have to add this 2/3
ROLLBACK; <-- You have to add this 3/3

For example:

CREATE OR REPLACE TRIGGER OWNER.TGR_XXX
AFTER
DELETE OR UPDATE
ON OWNER.TABLE
REFERENCING OLD AS OLD NEW AS NEW
FOR EACH ROW
DECLARE
cTipo VARCHAR2( 100 );
cHI_USUARIOSIS VARCHAR2( 1500 );
cHI_MAQUINA VARCHAR2( 1500 );
dHI_FECHASIS DATE;
cHI_FECHALOGON VARCHAR2( 1500 );
cHI_PROGRAMA VARCHAR2( 1500 );
PRAGMA AUTONOMOUS_TRANSACTION; <-- You have to add this 1/3
BEGIN

SELECT LOGON_TIME, OSUSER, MACHINE, PROGRAM
INTO cHI_FECHALOGON, cHI_USUARIOSIS , cHI_MAQUINA, cHI_PROGRAMA
FROM V$SESSION WHERE AUDSID = USERENV( 'SESSIONID' ) AND ROWNUM=1;

IF UPDATING THEN
cTipo := 'U';
ELSIF DELETING THEN
cTipo := 'D';
END IF;

INSERT INTO OYM.DSVERSION_ME_RW
HI_USUARIORED ,
HI_USUARIOSIS ,
HI_MAQUINA ,
HI_FECHASIS ,
HI_FECHARED ,
HI_FECHALOGON ,
HI_ACCION ,
HI_PROGRAMA )
SELECT
USER,
CHI_USUARIOSIS ,
CHI_MAQUINA ,
DHI_FECHASIS ,
SYSDATE ,
CHI_FECHALOGON ,
CTIPO,
CHI_PROGRAMA
FROM OWNER.TABLE_2
WHERE FIELD = :OLD.FIELD;
COMMIT; <-- You have to add this 2/3
EXCEPTION WHEN OTHERS THEN
DB_ERR_GRABA ( 0, 'OWNER.TGR_XXX:'||sqlerrm );
ROLLBACK; <-- You have to add this 3/3
END;
/

  ¶ 9:08 AM 0 comments

  The mystery of icon Displacement on Buttons on Oracle Developer for windows (Client/Server) up to Developer 6i (sp18) at least

Several times we had problems displaying icons, we handled several theories, like the cause was the amount of colors, and tried several solutions.
The test was complicated because if you set an icon misplaced and after an icon not misplaced by defaut, it was showed misplace on that button, so you had to reopen the canvas to get refresed.

Recently after a long sequence of test, the mistery was
solved. the problem resides in the name of the icon.
You can do the following test take an icon, and name as a,l,m,s (this words in the icon name causes the displacement) and create another copy naming anything else, but never use that letters, for example 01.
As you can see the same icon is displayed differently depending on the name of the icon, the most interesting was to found different levels of displacement.

Regards,  ¶ 1:03 PM 0 comments