More information here.

The next four Critical Patch Update release dates are:

October 12, 2010

January 18, 2011

April 19, 2011

July 19, 2011

Many thanks to the guys spent some time to collect and list the errors.

The list is not full, but really useful. As I am reading this book now, I will post all found errors not listed in the errata. Unfortunately, this is the only one book for 11g OCP upgrade.

Errata.

In the Errata is written -

p63 The bullet: The default ADR base directory IS $ORACLE_BASE/diag should read as follows:
The default ADR base directory IS $ORACLE_BASE (if ORACLE_BASE isn’t set, the directory would default to $ORACLE_HOME/diag).
This should be read as (this is an error in the Errata)
p63 The bullet: The default ADR base directory IS $ORACLE_BASE/diag should read as follows:
The default ADR base directory IS $ORACLE_BASE (if ORACLE_BASE isn’t set, the directory would default to $ORACLE_HOME/log).

In addition, I founded the following errors. First page number (if there are two page numbers) - pXXX is the page number in the book. If you read the book from the CD  – as book is divided by chapters and each chapter starts from page 1 – second page number is the page number from the current chapter. Thus

p222 chapter 3 p23 means that in the paper book it is page 222, in pdf for chapter 3 it is page 23. If there is only one page number, this is the page number in paper book.

p36: In the code example closing bracket and semicolon are missing – after fvalue =>’salapati’

p39: In the code example, capture_dir => 2008jan’ to be read capture_dir => ‘jan08′

p43(and further): Keyword for replay directory in wrc tool  is mistaken. It is written replay_dir, must be replaydir

p56: Under the block ‘Create the SQL Performance Analyzer Task’ is stated ‘Use the CREATE_ANALYSIS_TASK procedure…’ – CREATE_ANALYSIS_TASK is a function.

p66 Fourth bullet fom the bottom – GET_REPLAY_INFO doesn’t have replay_type parameter. The type of the report is specified by the parameter format from dbms_workload_replay.report

p88: First sentence – You can return to the ADRCI… – is not correct. After running the command show alert -tail, prompt comes without interruption. But if you run show alert, you will see the alert log in text editor(I got it by vi) and you have to close it as usual file close in vi.

p107: At the beginning of  exercise 2-2 is mentioned V$HM_CHECK_VIEW(wrong) – view name is V$HM_CHECK. Further, the first line from the second code block – there is a missing dot between dbms_hm and run_check

chapter 1 p58 – in the first code example, you have to execute dbms_sqlpa.execute_analysis_task, not dbms_sqltune.execute_analysis_task

p112 chapter 2 p36 , point 2  – problem_type_execution_type to be read  problem_type_execution_error
p113 chapter 2 p37 – EXECUTE_DIAGNOSTIC_TASK is EXECUTE_DIAGNOSIS_TASK, REPORT_DIAGNOSTIC_TASK is REPORT_DIAGNOSIS_TASK

p151 chapter 3 p5 – in the code example -  end_time => ’2007812-31 22:00:00 PST’, to be read end_time => ’2008-12-31 22:00:00 PST’
p153 chapter 3 p7 – !!! check dbms_workload_repository.select_baseline_metrics
In the errata is stated that the following line has to be added – ‘RETURN awr_baseline_metric_type_table PIPELINED;’
notes – 1. function name is select_baseline_metric, not select_baseline_metrics
2. in the errata is actually the description from Oracle documentation. If you want to get the metrics values, you should use
SELECT * FROM   TABLE(DBMS_WORKLOAD_REPOSITORY.select_baseline_metric(‘metric_name is here’));
p155 chapter 3 p9 Under ‘Moving Window AWR Baselines’  – change ‘the default retention period has been increased to 7 days’ with ‘the default retention period has been increased to 8 days’
p163 chapter 3 p17 – at the bottom – ‘ORA$AUTOTASK_SUB_PLAN gets 25 percent of the resources at the priority level 2′ – ORA$AUTOTASK_SUB_PLAN gets 5% on level 2. ORA$DIAGNOSTICS and OTHER_GROUPS takes 5% too, rest 85% are for INTERACTIVE_GROUP on level 2
p166 chapter 3 p20 – key parameters from CALIBRATE_IO description – max_ios to be read max_iops. num_disks parameter is wrong, it is num_physical_disks
p179 chapter 3 p33 – Note (after a last page line) If you haven’t XML DB installed, desc ‘resource_view’ will return error ORA-04043: object resource_view does not exist
p180 chapter 3 p34 – under point 3, ‘registration_password => ‘sammyy1′.-’ to be read as ‘registration_password => ‘sammyy1′,-’ – comma instead of dot
p185 chapter 3 p39 Under point 3 – ‘logical standby’ must be upper case – ‘LOGICAL STANDBY’ .Otherwise error is returned.
p196 chapter 3 p50 Under Creating an Encrypted Tablespace is stated that the default encryption is DES128. But it is not DES128(not existing), default is AES128(for tablespace encryption). By not specifying ‘using’ clause, AES128 will be used. For column encryption, default is AES192
p203 chapter 3 p57 first bullet ‘The remote database’ should be ‘The remote machine’
p208 chapter 3 p62 Answers – 1 question – ‘C is correct because an AWR baseline template helps you capture data for specific time periods in the past’ is
‘C is correct because an AWR baseline template helps you capture data for specific time periods in the future’

p219 chapter 4 p7 First sentence under Configuring Automatic SQL Tuning – (SY_AUTO_SQL_TUNING_TASK) is (SYS_AUTO_SQL_TUNING_TASK)
p221 chapter 4 p9 In the code examples, window name is specified by window_name=’… – must be window_name=>’…
p229 chapter 4 p17 first code example dbmns_sqltune is dbms_sqltune
p229 chapter 4 p17 In the code under step 2 there is a reference to dbms_sqlset – dbms_sqlset.load_sqlset. It must be dbms_sqltune.load_sqlset
p236 chapter 4 p24 The code at the page bottom is wrong. First, ALTER_SQL_PLAN_BASELINE is a function, not procedure or view(as it is mentioned). The code must be (attribute_name => ‘accepted-status’ is wrong)
declare
ret integer;
begin
ret := dbms_spm.alter_sql_plan_baseline(sql_handle => ‘SYS_SQL_a60a94a3cbf2353b’,
plan_name => ‘SQL_PLAN_ac2nnng5z4d9v8dd47f8f’,
attribute_name => ‘enabled’,
attribute_value => ‘YES’);
end;
p239 chapter 4 p27 Code at the bottom – exec dbms_spm.purge_sql_plan_baseline – there is no proc/function purge_sql_plan_baseline in dbms_spm. There is a function AUTO_PURGE_SQL_PLAN_BASELINE in not documented package dbms_spm_internal.
But I am not aware of this package.
p244 chapter 4 p32 (mentioned in the errata, but wrong) – ‘open mycursoror’ must be read as ‘open mycursor for’
p246 chapter 4 p34 First sentence after the code – (the valid_task_list parameter) is (the valid_table_list parameter)
p247 chapter 4 p35 – Under ‘Generating SQL Scripts’, “execute dbms_advior.create_file” is execute “dbms_advisor.create_file”

p268 chapter 5 p6 – The explanation about “alter diskgroup dgroupA offline disks in failuregroup controller1 drop after 4h;”
First it is failgroup, not failuregroup(and later in text). Second, it is written ‘the database take the disk group dgroupA offline only after waiting for four hours’.
It must be ‘the database take the disk group dgroupA offline and drops it after four hours’
p277 chapter 5 p15 At the beginning of the page – ‘The default for both the compatible.asm and compatible.rdbms attributes is 10′ – default value is not 10, but 10.1
p279 chapter 5 p17 – It is not an error, just addendum(could appear in the exam, book is for 11gR1) – in 11gR2 there is a new parameter – compatible.advm It determines whether the disk group can contain Oracle ASM volumes.
The value must be set to 11.2 or higher. Before setting this attribute, the compatible.asm value must be 11.2  or higher. Also, the Oracle ADVM volume drivers must be loaded in the supported environment.
p280 chapter 5 p18 – under ‘Changes in the check Command’ – ‘If there are any consistencies’ must be ‘If there are any inconsistencies’
p285 chapter 5 p23 4th line from the top – ‘Unless you specify the -i flag,’ – the flag is ‘I’, capital.
p292 chapter 5 p30 Code examples are not correct. There is no column partitioning_type in dba_tab_partitions. There is a column partitioning_type in dba_part_tables, but this partitioning type is for the table – RANGE, not partition by partition.
p293 chapter 5 p31 First sentence after the code  – ‘When new data that has an ORDER_DATE column…’ must be ‘When new data that has an TIME_ID column…’
p293 chapter 5 p31 Text before ‘Moving the Transition Point’ – 2nd bullet ‘You can perform interval partitioning on an index-organized table’ – WRONG! You can’t perform interval partitioning on an index-organized table.
p294 chapter 5 p32 Bullets at the end of the page (las is on p33) column name TIME_ID is transaction_date
p306 chapter 5 p44 ‘alter table orders add partition’ statement is not correct – 01-feb-2007 is lower than the highest bound and this causes ORA-14074. Other value has to be used, f.i. 01-feb-2010
p317 chapter 5 p55 Self test answers 3 – A is stated as a correct answer, but the correct answer is D, because you must first advance the compatible.asm attribute before you advance the compatible.rdbms attribute
p293 chapter 5 p31 First sentence after the code  – ‘When new data that has an ORDER_DATE column…’ must be ‘When new data that has an TIME_ID column…’
p293 chapter 5 p31 Text before ‘Moving the Transition Point’ – 2nd bullet ‘You can perform interval partitioning on an index-organized table’ – WRONG! You can’t perform interval partitioning on an index-organized table.
p294 chapter 5 p32 Bullets at the end of the page (las is on p33) column name TIME_ID is transaction_date
p306 chapter 5 p44 ‘alter table orders add partition’ statement is not correct – 01-feb-2007 is lower than the highest bound and this causes ORA-14074. Other value has to be used, f.i. 01-feb-2010
p317 chapter 5 p55 Self test answers 3 – A is stated as a correct answer, but the correct answer is D, because you must first advance the compatible.asm attribute before you advance the compatible.rdbms attribute

p329 chapter 6 p9 Last sentence on the page bottom – it is 60% for SGA and 40% for PGA (instead SGA, PGA is mentioned)
p344 chapter 6 p24 Code for creating extended statistics, last line before ‘end;’  – it is ‘(cust_state_province’,country_id)’); – must be ‘(cust_state_province,country_id)’);
p351 chapter 6 p31 Shortly before page end, in the sentence ‘You can see that the result cache is disabled because you set the initialization parameter max_result_cache_size to zero’ – parameter is not max_result_cache_size, but result_cache_max_size
p353 chapter 6 p33 At the page bottom – V$RESULT_CACHE_OBJECTS is mentioned twice with different descriptions. Actually if you merge both descriptions you get the full V$RESULT_CACHE_OBJECTS description
p355 chapter 6 p35 ‘SQL> show parameter optimizer_use_pending_statistics’ to be read ‘SQL> show parameter result_cache_mode’
p361 chapter 6 p41 – bullet client_result_cache_size – ‘As I explain later, you can override this parameter with the server-side configuration parameter oci_result_cache_max_size’ – oci_result_cache_max_size is parameter in sqlnet.ora(client)
p361 chapter 6 p41  bullet client_result_cache_size -
‘If you disable client result caching on the server itself,the client result cache will remain disabled, even if you set the client_result_cache_size parameter to a positive value on the client’ – I suggest it has to be read like
‘If you disable client result caching on the server itself,the client result cache will remain disabled, even if you set the oci_result_cache_max_size parameter to a positive value on the client’
Take a look here – http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10646/oci10new.htm – for better explanation of oci_result_cache_ parameters
p367 chapter 6 p47 CERTIFICATION SUMMARY – Second sentence, replace DDM with ADDM
p370 chapter 6 p50 Second bullet under Enhancements in Optimizer Statistics Collection – view is not DBA_TAB_STATS_PREFS, but DBA_TAB_STAT_PREFS
p370 chapter 6 p50 Sixth bu2C you can override this parameter with the server-side configuration parameter oci_result_cache_max_size’ – oci_result_cache_max_size is parameter in sqlnet.ora(client)
p361 chapter 6 p41  bullet client_result_cache_size -
‘If you disable client result caching on the server itself,the client result cache will remain disabled, even if you set the client_result_cache_size parameter to a positive value on the client’ – I suggest it has to be read like
‘If you disable client result caching on the server itself,the client result cache will remain disabled, even if you set the oci_result_cache_max_size parameter to a positive value on the client’
Take a look here – http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10646/oci10new.htm – for better explanation of oci_result_cache_ parameters
p367 chapter 6 p47 CERTIFICATION SUMMARY – Second sentence, replace DDM with ADDM
p370 chapter 6 p50 Second bullet under Enhancements in Optimizer Statistics Collection – view is not DBA_TAB_STATS_PREFS, but DBA_TAB_STAT_PREFS
p370 chapter 6 p50 Sixth bullet under Enhancements in Optimizer Statistics Collection – procedure is not SET_PREFS, there are SET_DATABASE_PREFS, SET_GLOBAL_PREFS, SET_SCHEMA_PREFS, SET_TABLE_PREFS
p370 chapter 6 p50 Last bullet on the page – parameter is optimizer_use_pending_statistics, not optimizer_pending_statistics
p371 chapter 6 p51 Last bullet before ‘Result Cache’ – ‘…to collect extension statistics’ is ‘…to collect expression statistics’
p371 chapter 6 p51 Before last bullet – DBMS_RESULT_CACHE is a package, not procedure
p378 chapter 6 p58 Answer to question 6 – D is stated as true, but the true answer is B
p379 chapter 6 p59 Answer to question 12 – option is not ‘auto’, but ‘force’

p387 chapter 7 p5 In code example – connect auxiliary sys/oracle@prod1 must be connect auxiliary sys/oracle@prod2 (check before post)
p393 chapter 7 p11 Under Managing Multisection Backups – no views RC_BACKUP_DATAFILE, RC_BACKUP_SET. I have no idea what was the idea… There are v$backup_datafile and v$backup_set
p393 chapter 7 p11 Under Managing Multisection Backups – select statement must be ‘select pieces, multi_section from v$backup_set;’ – there is no column piece but pieces and pieces and multi_section are in v$backup_set
The sentence before the select statement must be ‘…the following query on the V$BACKUP_SET view:’
p396 chapter 7 p14 – On the job – ‘You can create archival backups only if you are using a recovery catalog’ – not true, if KEEP FOREVER is used then catalog is needed. By KEEP UNTIL… – no catalog is mandatory
p396 chapter 7 p14 at the bottom – ‘change copy of database controlfile nokeep;’ must be ‘change backup of database controlfile nokeep;’
p402 chapter 7 p20 sql statement at the page end – this statement is valid for 11gR1(the output is not the same as shown here).
For 11gR2, there is no is_default column in v$rman_compression_algorithm, the column is IS_VALID and there are no ZLIB and BZIP2 algorithms, but BASIC, LOW, MEDIUM, HIGH
p410 chapter 7 p28 Page bottom – connect target / catalog virtual1/virtual1@catdb; – should be separated in two commands (at least for me it had to)
connect target virtual1/virtual1@catdb;
connect catalog virtual1/virtual1@catdb; – and then ‘register database;’
p420 chapter 7 p38 – sql statements for creating flachback archive  – correct is ‘create flashback archive …’, not ‘create flashback data archive …’ – word ‘data’ must be omitted
p421 chapter 7 p39 Under ‘Altering a Flashback Data Archive’ there are two identical examples – ‘alter flashback archive flash1 add tablespace …’ with different explanation. But there is no option ‘adds space to the flashback archive’. You could change quota or add tablespace.
p422 chapter 7 p40 – Under  ‘Enabling and Disabling Flashback Data Archiving’ it said ‘You must be either the DBA or have the flashback data archive system privilege and the create tablespace system privileges to turn flashback logging on for a table’.
The privilege is not ‘flashback data archive’, but ‘flashback archive’. And you don’t need ‘create tablespace’ to enable flashback, just ‘flashback archive’ to selected archive or ‘flashback archive administer’.
p425 chapter 7 p43 as_of clause is “as of” – no underscore
p426 chapter 7 p44 Code under Generating Reports – date format must be ‘YYYY-MM-DD HH24:MI:SS’, not ‘YYYY-MM-DD HH24:MI:SS’ – there are still 24 hours in day-night period
p428 chapter 7 p46 Under Prerequisites for Flashback Transaction Backout – text ‘The first privilege grants the user HR the flashback system privilege…’ should be something like ‘First grant is the execute privilege on dbms_flashback package to user hr’.
p428 chapter 7 p46 FLASHBACK.TRANSACTION_BACKOUT description – there is no argument numberofxids – it is numtxns.
p429 chapter 7 p47 ‘options’ argument for FLASHBACK.TRANSACTION_BACKOUT – noconflict_only must be nonconflict_only. Mentioned in the errata, but it is wrong – must be ‘nonconflict_only’
p440 chapter 7 p58 Question 13 – privilege to be granted in 1. is ‘recovery_catalog_owner’, not ‘recovery catalog owner’
p443 chapter 7 p61 – Answer to question 1 – I think A, B, C are correct. The best is to take a look on the documentation to clarify this question completely (Oracle® Database Backup and Recovery Reference).
In general, you can specify log_file_name_convert and db_file_name_convert in set clause  – the example below is from Oracle Documentation
DUPLICATE TARGET DATABASE TO dup1
FOR STANDBY
FROM ACTIVE DATABASE
PASSWORD FILE
SPFILE
PARAMETER_VALUE_CONVERT ‘/disk1′, ‘/disk2′
SET DB_FILE_NAME_CONVERT ‘/disk1′,’/disk2′
SET LOG_FILE_NAME_CONVERT ‘/disk1′,’/disk2′
SET SGA_MAX_SIZE 200M
SET SGA_TARGET 125M;
So, you can set DB_FILE_NAME_CONVERT under SPFILE…SET clause as well LOG_FILE_NAME_CONVERT.
PARAMETER_VALUE_CONVERT is out of SET clause. You can set DB_FILE_NAME_CONVERT outside SET clause too – but the setting outside of the SPFILE clause takes precedence.
For example, if you specify DB_FILE_NAME_CONVERT twice in the DUPLICATE command, both in the SPFILE clause and outside of the SPFILE clause, then the setting outside of the SPFILE clause takes precedence.
p446 chapter 7 p64 Answer to question 17 – Which of the following items must you specify when you create a flashback data archive? B and D are mentioned as correct. Well, if you omit flashback archive name, you get error. Only quota is not mandatory.
Either the question was not asked correctly, or the answer is badly formed – I can’t understand ‘C is incorrect because the flashback data archive isn’t mandatory—you can omit the attribute as long as you have
already created a default flashback data archive for the database’ – what is the relation with creating flash archive? You don’t need to specify flash archive by enabling the feature for a table – when there is a default flashback,
but for creation flashbak – you do have to specify name -  create flashback archive myflash tablespace flash_tbs retention 1 year;
p446 chapter 7 p64 – Answer to question 18 – B is valid answer only if flashback has no quota on the tablespace. If there is a quota, then adding space to the tablespace will not help. The question is a bit ambiguous.

p454 chapter 8 p6 – in example sql code for table creation, opening brace for table columns is missing – (id number,…  (on page 7 too)
p456 chapter 8 p8 Under Managing and Monitoring SecureFiles – procedure is SETOPTIONS, not ETOPTIONS
p457 chapter 8 p9 In both sql’s for creating table, the brace after ‘store as ….’ must be removed. And tables need a primary key – otherwise you get
ORA-12089: cannot online redefine table “TAB1″ with no primary key
p459 chapter 8 p11 – Explicit Table Locking – ‘lock table’ statement explanation is ambiguous.
lock table…in lockmode mode [nowait | wait integer] – lockmode is one of [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE. Then comes word ‘mode’ and then wait/nowait with integer
lock table foo in share mode wait 10; – f.i.
p461 chapter 8 p13 create spfile from memory; returns ‘ORA-32002: cannot create SPFILE already being used by the instance’ – when you try from open instance. You have to specify filename/path – create spfile=’<filename>’ from memory;
p467 chapter 8 p19 under ‘Using Real Native Compilation’ – ‘The parameter can take two values, interpreted and compiled’ – wrong, the parameter can take interpreted and native. Later in text also ‘compiled’ is mentioned – it is ‘native’.
In the next sentence, the author means ‘interpreted’, not ‘compiled’.
p468 chapter 8 p20 The last sentence in page bottom – ‘Also, even after you change the compilation mode, say from compiled to native, PL/SQL units that the database has already compiled will be recompiled in the original compilation mode’
I find it a bit ambiguous – if you change plsql_code_type from native(not compiled) to interpreted, plsql units compiled in native mode, stays in native mode. This couls be checked by select name, PLSQL_code_type from user_plsql_object_settings;
p473 chapter 8 p25 ‘Monitoring Table Compression’ – in last sentence in this block column name is COMPRESS_FOR, not COMPRESSED_FOR.
!!!  Important difference – the output from select statement is for 11gR1. In 11gR2, in the same sql’s output ‘DIRECT LOAD ONLY’ is changed with ‘BASIC’ and ‘FOR ALL OPERATION’ with ‘OLTP’

You can also find this errata here.

If you like this, you could spend 3$ and make my day

You can test it by simply creating dummy table (don’t insert any data into it) and then try to export the table.
>sqlplus user/pass

SQL*Plus: Release 11.2.0.1.0 Production on Fri Apr 9 15:48:54 2010

Copyright (c) 1982, 2009, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options

SQL> create table foo(id number);

Table created.

SQL>exit

>exp file=foo.dmp log=goo.dmp tables=foo userid=user/pass

Export: Release 11.2.0.1.0 – Production on Fri Apr 9 15:48:00 2010

Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options
Export done in WE8MSWIN1252 character set and UTF8 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)

About to export specified tables via Conventional Path …
EXP-00011: USER.FOO does not exist
Export terminated successfully with warnings.

Well, I am pretty sure that the table exists – even without any data in it.

The reason for this behavior is 11.2 new feature ‘Deferred Segment Creation‘ – the creation of a table sent is deferred until the first row is inserted.

As a result, empty tables are not listed in dba_segments and are not exported by exp utility.

This feature is controlled by the database parameter deferred_segment_creation. It has default value of TRUE. If you set it by FALSE, any newly created table AFTER the change will be exported – nevertheless if it is empty or not.

>sqlplus system/pass

SQL*Plus: Release 11.1.0.7.0 – Production on Fri Apr 9 15:59:02 2010

Copyright (c) 1982, 2008, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options

SQL> alter system set deferred_segment_creation=false;

System altered.

SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options

>sqlplus user/pass

SQL*Plus: Release 11.1.0.7.0 – Production on Fri Apr 9 15:59:20 2010

Copyright (c) 1982, 2008, Oracle.  All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options

SQL> create table foo2(id number);

Table created.

SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options

>exp file=foo2.dmp log=foo2.log tables=foo2 userid=user/pass

Export: Release 11.1.0.7.0 – Production on Fri Apr 9 15:59:54 2010

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 – 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining
and Real Application Testing options
Export done in WE8MSWIN1252 character set and UTF8 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)

About to export specified tables via Conventional Path …
. . exporting table                           FOO2          0 rows exported
Export terminated successfully without warnings.

—————————————————————————————————————–

Note: Deferred Segment Creation option is not supported in 11gR2 Standard Edition

emctl stop dbconsole

open the file $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_service_name/config/server.xml
and add the following line before the </application-server> element:

<application name=”dva” path=”$ORACLE_HOME/dv/jlib/dva_webapp.ear” parent=”default” start=”true” />

OC4J_DBConsole_service_name is OC4J_DBConsole_<machine name>_<db sid>
F.i. -  OC4J_DBConsole_my_machine_db1
Here my_machine is machine name, db1 is database name.

On Windows systems, replace $ORACLE_HOME with the absolute path to your Oracle Database home.

Open the file $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_service_name/config/http-web-site.xml and add the following line before the </web-site> element:

<web-app application=”dva” name=”dva_webapp” load-on-startup=”true” root=”/dva” shared=”true”/>

Finally start dbconsole again -

emctl start dbconsole

DVA could be accessed on your dbconsole url – port 5501 -

my_machine:5501/dva/

1. There is no database associated with this Oracle Home

This is easier. Stop all processes associated with this Oracle Home. Then go to directory $ORACLE_HOME/rdbms/lib and execute

cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk dv_on lbac_on ioracle

Now continue with database creation and ensure that Database Vault option is selected(using dbca).

2. There is a database associated with this Oracle Home

Stop all processes associated with this Oracle Home -database(s), listeners, etc. Then go to directory $ORACLE_HOME/rdbms/lib and execute

cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk dv_on lbac_on ioracle

Now startup the database and execute the script catols.sql as user SYS -

SQL>@?/rdbms/admin/catols.sql
The script will shutdown the database and the last lines from the execution show
…
Database closed.
Database dismounted.
ORACLE instance shut down.

Start the database.

Finally, database vault option must be enabled. Easiest way is by Database Configuration Assistant – dbca.

Start dbca tool and select ‘Configure Database Option’. Click Next.

Select designated database. Click Next.

Select ‘Oracle Database Vault’ option. Click Next.

Enter name and password for Database Vault Owner and Database Vault Account Manager. The Database Vault Owner account manages Database Vault roles and configuration. The Database Vault Account Manager account is used to manage database user accounts. You can choose whatever username and password you want, but they should comply with the password policy -at least 8 and at most 30 characters, must contain at least one alphabet, one digit and one non-alphanumeric character.

Click ‘Finish’ to finish the process.

ORA-01450: maximum key length (6398) exceeded

Database has character set AL32UTF8, national character set UTF8  and uses CHAR semantic (nls_length_semantics).

If charset is AL32UTF8 and semantic is BYTE, there is no error by database creation. Also if semantic is CHAR, but charset is WE8MSWIN1252 f.i. – also there is no problem.

It seems that by using both AL32UTF8 and CHAR semantic, the error appears by adding database vault.

The problematic statements actually is

ALTER TABLE DVSYS.”IDENTITY_MAP$”
ADD CONSTRAINT “IDENTITY_MAP_UK1″
UNIQUE(IDENTITY_ID#,FACTOR_LINK_ID#,
OPERATION_CODE_ID#,OPERAND1,OPERAND2)
ENABLE;

The following workarounds are possible.

1. Use block size 16K – the error doesn’t appear. But changing block size should be done only after performance tests, because this change could hardly influence database performance.

2. Use separate tablespace with block size 16K – only for database vault system objects. If you use database template, just add the following under the <CommonAttributes> section -

<option name=”DV” value=”true”>
<tablespace id=”DBVAULT”/>
</option>

and add tablespace DBVAULT (as well datafile) description later in the template file. 50M is enough as a initial tablespace size.

Of course, do not forget to set db_16k_cache_size to some appropriate value – for instance 50M.

Then database creation runs without problems and database with DB Vault, charset AL32UTF8 and and CHAR semantic is created successfully.

move the block
<?php if ( topic_is_open( $bb_post->topic_id ) ) : ?>
<?php post_form(); ?>
<?php else : ?>
<h2><?php _e(‘Topic Closed’) ?></h2>
<p><?php _e(‘This topic has been closed to new replies.’) ?></p>
<?php endif; ?>

after first

<div class=”nav”>
<?php topic_pages(); ?>
</div>

And you got it.

find get_thread( $topic_id, $page ) in /topic.php and change it to get_thread( $topic_id, $page, true )

Simple.

“clicked”=>array(
“type”=>”INT”,
“form invisible”,
“sorta”
),
“responded”=>array(
“type”=>”INT”,
“form invisible”,
“sorta”
),

and sorting by field will disappear(small icons next to the field as well link).

<?php if( $this->get(“friendmailLink”) ): ?>
<td style=’padding-left: 20px;’><div class=’friend’><?php echo $this->get(“friendmailLink”) ?></div></td>
<?php endif; ?>

That it’s.