Follow the accepted answer from the following post: Re: Unable to open MSDB node if you are using a named SQL Server instance and you can't access the SSIS packages within the MSDB database.

You will experience a 'Login Timeout' exception until you edit the XML file mentioned in the post. By default, Microsoft is configured to connect to the DEFAULT instance only; short of modifying this file, there is no way of specifying a different Database Service for Integration Services to use.

Labels: Bugs, SQL Server

When installing Oracle Warehouse Builder - specifically 10g Release 2 - there are a couple of Oracle bugs that need to be addressed:

Depending upon your platform, you may encounter:

Error in invoking target 'isqlldr' of makefile 
'$ORACLE_HOME/rdbms/lib/ins_rdbms.mk'.

The following Oracle Forum posting identifies the workaround:

Thread: OWB paris install on 10g rel1 RAC cluster

Depending upon your platform, you may also encounter the following bug while installing the optional Oracle Workflow - version 2.6.4 - component.

After issuing this command:

$ORACLE_HOME/wf/install/wfinstall.csh

You will encounter an error which mentions WorkflowCA: WFTLoad Exception: could not upload the wfstd.wft file.

The above issues is resolved with patch:

4778368 - WFTLOAD EXCEPTION:COULD NOT UPLOAD FILE /RDBMS/10201/WF/RES/US/WFSTD.WFT

Labels: Bugs, Data Warehousing

Upon moving to 10g, you may experience poor performance when using RMAN with a 10g recovery catalog. Resync operations, in particular will run extremely slow, increasing the overall amount of time your backup jobs take to run to fruition.

This is Bug #5047758 as documented in Metalink note 247611.1.

To remedy this, issue the following command and/or include it in any stored scripts you might be using:

sql "alter session set optimizer_mode=RULE";

Or nest in your stored script or run block:

CREATE SCRIPT SAMPLE_SCRIPT {
sql "alter session set optimizer_mode=RULE";
}

Oracle also recommends that in response you gather the fixed objects' statistics via: exec dbms_stats.gather_fixed_objects_stats() on the recovery catalog database(s) in question.

Labels: Bugs, RMAN

There is a known bug when installing Oracle Database 10g version 10.1.0.2 on Windows platforms: Bug #3617107. Specifically, the OracleCSService doesn't install correctly (it will show as 'Starting'), when installing the software as a non-local user (i.e. using an Active Directory account).

To get the software installed correctly, you can reference the following Metalink notes - 276801.1 and 619166.999 - or you can insure that the 'ORA_DBA' group is added to local 'Administrator' group and that the local 'System' user is added to the local 'Administrator' group before running the installer executable.

Once you have a good software installation, you can either create the ASM instance using the dbca or you can create manually:

C:\Documents and Settings\oracle>set ORACLE_SID=+ASM

C:\Documents and Settings\oracle>set ORACLE_HOME=c:\apps\oracle\product\10g

C:\apps\oracle\product\10G\BIN>oradim -NEW -ASMSID +ASM -SYSPWD yomama 
Instance created.

C:\apps\oracle\product\10G\BIN>cd ..\database

C:\apps\oracle\product\10G\database>notepad.exe INIT+ASM.ORA

C:\apps\oracle\product\10G\database>dir 

 Directory of C:\apps\oracle\product\10G\database 

06/07/2005  02:53p      <DIR>          . 
06/07/2005  02:53p      <DIR>          .. 
06/07/2005  12:41p      <DIR>          archive 
06/07/2005  02:54p                  55 INIT+ASM.ORA 
06/07/2005  12:32p              31,744 oradba.exe 
06/07/2005  02:53p               2,560 PWD+ASM.ORA 
               3 File(s)         34,359 bytes 
               3 Dir(s)   6,115,950,592 bytes free

C:\apps\oracle\product\10G\database>sqlplus "/ as sysdba" 

SQL*Plus: Release 10.1.0.2.0 - Production on Tue Jun 7 14:55:06 2005 

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

Connected to an idle instance.

SQL> startup 
ASM instance started 

Total System Global Area  100663296 bytes 
Fixed Size                   787648 bytes 
Variable Size              99875648 bytes 
Database Buffers                  0 bytes 
Redo Buffers                      0 bytes 
ORA-15110: no diskgroups mounted

On Windows platforms, disks need to be 'stamped' using one of the ASMTool executables, before you can add them to a diskgroup, etc. The following document has a good description of this process on page 26: Dell Oracle Deployment White Paper.

Labels: ASM, Bugs