Dicas ORACLE DBA

[oracle@mumanga ~]$ adadmin adadmin: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directory Solution: [oracle@mumanga ~]$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib/ [oracle@mumanga ~]$ adadmin Copyright (c) 2002 Oracle Corporation Redwood Shores, California, USA Oracle Applications AD Administration Version 12.0.0

The file "fmrweb.res" contains a keyboard map. This map is used by Oracle Forms Server to detect key strokes entered in the user's browser and map them to Forms actions. The map assumes that the keyboard is similar to a VT100 keyboard. Therefore to change / customize mapping, one needs to modify the fmrweb.res file located under: + R12: $ORACLE_HOME/forms/admin/resource/US + R11i: $ORACLE_HOME/forms60/admin/resource/US Note: One needs to bounce the forms services for changes to take effect In case of multiple languages modify the appropriate mapping files (fmrweb.res) for that language E.g: "fmrweb .res" and "fmrpcweb .res", where is the Oracle language code.

SELECT FAV.APPLICATION_SHORT_NAME, FAV.APPLICATION_NAME,FRV.RESPONSIBILITY_KEY, FRV.RESPONSIBILITY_NAME FROM FND_APPLICATION_VL FAV, FND_RESPONSIBILITY_VL FRV WHERE FRV.APPLICATION_ID=FAV.APPLICATION_ID ORDER BY FRV.RESPONSIBILITY_NAME Using fnd_user_pkg: Input (Mandatory) -- username: User Name -- resp_app: Application Short Name -- resp_key: Responsibility Key -- security_group: Security Group Key -- description: Description -- start_date: Start Date -- end_date: End Date Sample Usage: set serveroutput on BEGIN fnd_user_pkg.addresp ('Username','OE','ORDER_ENTRY_SUPER_USER','STANDARD','Responsability added by Denilson Using PL/SQL',SYSDATE, null); COMMIT; DBMS_OUTPUT.put_line ('Responsibility Added Successfully'); EXCEPTION WHEN OTHERS THEN DBMS_OUTPUT.put_line('Responsibility is not added due to'); DBMS_OUTPUT.PUT_LINE('ERROR: ...

11G has a new feature called Invisible Indexes. An invisible index is invisible to the optimizer as default. Using this feature we can test a new index without effecting the execution plans of the existing sql statements or we can test the effect of dropping an index without dropping it. SQL> create table teste_ii (a number, b varchar2(10)); SQL> create index idx_invisible on teste_ii(id); begin for i in 1..20 loop insert into teste_ii(a,b) values(i,'TESTE'||i); end loop; end; / commit; SQL> select * from teste_ii where a=10; A B ---------- ---------- 10 TESTE10 SQL> explain plan for 2 select * from teste_ii where a=10; Explained SQL> sELECT * FROM TABLE(dbms_xplan.display); PLAN_TABLE_OUTPUT -------------------------------------------------------------------------------- Plan hash value: 726495292 -------------------------------------------------------------------------------- | Id | Operation | Name | Rows |...

For RMAN jobs, you can query the following columns in the V$SESSION_LONGOPS dynamic view: SID - The session ID for the RMAN channel SERIAL# - The serial number of the server session OPNAME - A description of what the row includes, such as RMAN: datafile copy, RMAN: full datafile backup, RMAN full datafile restore, RMAN: aggregate input, or RMAN: aggregate output CONTEXT - The context associated with the row, which is 2 for rows pertaining to backup output and 1 for other types of rows, except rows associated with proxy copies SOFAR - The work completed at the time the query is issued, which is the number of blocks read for image copies, the number of blocks read for files being backed up, the number of blocks written to the backup piece for backups, the number of blocks processed by a single job step for restores, and the number of files copied for proxy copies TOTALWORK - The work to be performed at the time the query was issued, which is the total number of blocks in the ...

Using Virtual Columns on 11g: Indexes defined against virtual columns are equivalent to function-based indexes. Virtual columns can be referenced in the WHERE clause of updates and deletes, but they cannot be manipulated by DML. Tables containing virtual columns can still be eligible for result caching. Functions in expressions must be deterministic at the time of table creation, but can subsequently be recompiled and made non-deterministic without invalidating the virtual column. In such cases the following steps must be taken after the function is recompiled: Constraint on the virtual column must be disabled and re-enabled. Indexes on the virtual column must be rebuilt. Materialized views that access the virtual column must be fully refreshed. The result cache must be flushed if cached queries have accessed the virtual column. Table statistics must be regathered. Virtual columns are not supported for index-organized, external, object, cluster, or temporary tables. The expression use...

CONN DENILSON/DENILSON@ORCL SQL> CREATE TABLE teste(x number); Table created SQL> CREATE UNIQUE INDEX ix_teste ON teste(x); Index created SQL> begin 2 for i in 1..20 3 loop 4 insert into teste(x) values(i); 5 end loop; 6 end; 7 / PL/SQL procedure successfully completed SQL> COMMIT; Commit complete CONN DENILSON/DENILSON@ORCL2 SQL> CREATE TABLE teste(x number); Table created SQL> CREATE UNIQUE INDEX ix_teste ON teste(x); Index created SQL> begin 2 for i in 1..20 3 loop 4 insert into teste(x) values(i); 5 end loop; 6 end; 7 / PL/SQL procedure successfully completed SQL> COMMIT; Commit complete SQL> DELETE FROM teste WHERE x = 10; 1 row deleted SQL> COMMIT; Commit complete CONN DENILSON/DENILSON@ORCL SQL> ALTER SESSION SET max_dump_file_size=unlimited; Session altered. SQL> ALTER SESSION SET timed_statistics = true; Session altered. SQL> ALTER SESSION SET statistics_level = ALL ; Session altered. SQL> ...