Connectig to olap from jdev --- a succes???

Question

1. Install Oracle 9i Release 2 (9.2.0.1) Enterprise Edition with the General purpose database configuration (Data warehouse works as well). At the end of the installation I chose the password management button to change passwords for the few necessary accounts: SYS, SYSTEM, OLAPSYS, SH.
2. Download the p3948480_9206_WINNT.zip from metalink, the 9.2.0.6 patchset
3. Shut down any existing Oracle9i database instances with normal or immediate priority. Stop all listener and other services running in the Oracle home directory where you want to install the patch set.
4. unzip the content of thepatch to a temp directory
5. start setup.exe under the temp directory (it will start the Oracle Universal installer 10.1.0.3)
6. install the patchset to your Oracle home, selecting the source in the temp_dir\stage\products.jar file
7. review carefully the post-installation tasks for the patchset:
Review the following sections before upgrading a database (quote from the patchset html readme):
8.2.1.1If JServer is part of the installation ensure that there is at least 10 MB of free space allocated to the SYSTEM tablespace.
8.2.1.2 Check XDB Tablespace Size
For RAC installations, ensure that there is at least 50 MB of free space allocated to the XDB tablespace.
8.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters
Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters as follows:
Start the database:
SQL> STARTUP
If necessary, enter the following command to determine whether the system uses an initialization parameter file (initsid.ora) or a server parameter file (spfiledbname.ora):
SQL> SHOW PARAMETER PFILE;
This command displays the name and location of the server parameter file or the initialization parameter file.
Determine the current values of these parameters:
SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
If the system is using a server parameter file:
If necessary, set the value of the SHARED_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;
If necessary, set the value of the JAVA_POOL_SIZE initialization parameter to at least 150 MB:
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;
If the system uses an initialization parameter file, if necessary, change the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization parameters to at least 150 MB in the initialization parameter file (initsid.ora).
Shut down the database:
SQL> SHUTDOWN
8.2.2 Upgrade the Database
After you install the patch set, you must complete the following steps on every database associated with the upgraded Oracle home:
Log on as a member of the Administrators group to the computer where the Oracle components are installed.
Use SQL*Plus to login to the database as the SYS user with SYSDBA privileges:
sqlplus /NOLOG
CONNECT SYS/password AS SYSDBA
Enter the following SQL*Plus commands:
SQL> STARTUP MIGRATE
SQL> SPOOL patch.log
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catpatch.sql
SQL> SPOOL OFF
Restart the database:
SQL> SHUTDOWN
SQL> STARTUP
Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql
9. Download the p4156468_9206_WINNT.zip patch for RDBMS and unzip in a temp dir
10. Download the p2617419_10102_GENERIC.zip patch for OPATCH
11. Go through:
# Pre-Install Instructions:
# Perform a clean shutdown of all Oracle databases, Oracle listeners, Oracle agents etc. that
# run from the Oracle Home where you install this patch.
# Stop all oracle services , Distributed Transaction Coordinator and other applications that use Oracle Client.
# This may include Webservers if any, that load Oracle client in the mid tier.
# Patch Installation Instructions:
# This patch must be installed using the OPatch utility which depends
# upon Perl. For details of where to get OPatch / Perl and how to use
# OPatch to install this patch please refer to MetaLink Note:189489.1
# To apply the patch, make sure the ORACLE_HOME environment variable is
# set to the correct Oracle Home which needs to be patched:
# > set ORACLE_HOME=<Oracle Home Path>
# Then set your current directory to the directory where the patch is
# located, e.g.:
# > cd 4156468
# Ensure that the directory containing the OPatch script appears in
# your Path; then enter the following command:
# > perl opatch.pl apply
# Post-Install Instructions:
# 1) If Oracle Ultra Search is installed, run the following:
# sqlplus /nolog
# SQL> connect / as sysdba
# SQL > alter session set current_schema=WKSYS;
# SQL > @%ORACLE_HOME%\ultrasearch\admin\wk0meta.plb
# SQL > @%ORACLE_HOME%\ultrasearch\admin\wk0ds.plb
# Restart the Oracle Http server and jserv.
# 2) SQL> connect / as sysdba
# SQL> @%ORACLE_HOME%\rdbms\admin\dbmsspc.sql
# SQL> @%ORACLE_HOME%\rdbms\admin\prvtspad.plb
# 3) Finally, to compile any invalid PL/SQL objects
# This scripts takes a positive integer parameter indicating the
# number of parallel recompilation threads desired. If this parameter
# is set to 0 or NULL, this script derives a value based on the
# CPU_COUNT database parameter. If the parameter is set to 1,
# sequential recompilation is used.
# SQL> connect / as sysdba
# SQL> shutdown immediate
# SQL> startup
# SQL> @%ORACLE_HOME%\rdbms\admin\utlrp.sql
12. Install JDeveloper 9.0.4 (download it from OTN and just unzip it in a directory ... it doesn't require an oracle home)
13. Install BI Beans 9.0.4 (download it from OTN as well), run the setup.exe that comes with it and in the destination oracle home select the directory where you installed JDeveloper and give an oracle home name to it)
14. Install the BIBDEMO schema:
Create a directory on the computer that is running the Oracle9i database. This install_home directory is the location to which you will upload the data files that are required to build the BIBDEMO schema.
On the computer where BI Beans is installed, locate the bibeans_home\bibdemo_schema folder (where bibeans_home is the root folder of your BI Beans installation). Copy all of the files found in this folder to the install_home folder on your server machine.
Open a DOS prompt and navigate to the install_home folder.
Run bibdemo.bat to install the schema, using the following syntax:
bibdemo.bat <path to Oracle database files >
For example, for an instance named my9iService, enter the following:
bibdemo.bat D:\OraHome1\oradata\my9iService
You are prompted for the password for the sys as sysdba user.
The script takes approximately 15 minutes to run, depending on the machine specifications. It is normal to see some error messages while the script is running. In addition, when materialized views are being created in the database, the script will appear to stop; this is also normal. A clear message will tell you when the script has completed.
The log files (*.log) that are generated by the installation script are stored in the folder from which you ran the script.
15. Install the BI Beans Catalog (BIBCAT schema):
On your local machine, open a command prompt at Oracle_home/bibeans/bin where Oracle_home is the directory where JDeveloper is installed. When you installed BI Beans, you made this directory an Oracle Home.
Set the environment variable JDEV_ORACLE_HOME to the Oracle Home directory.
Ensure that the environment variable JAVA_HOME is set to the directory where the JDK is installed.
If the environment variable JDBC_CLASSPATH is not set, then installing the Catalog sets it to ORACLE_HOME/bibeans/jdbc/lib_92, the directory that contains the JDBC files that are required by BI Beans. However, if JDBC_CLASSPATH is already set, then you must ensure that it references a directory that contains an appropriate version of the JDBC files (classes12.jar and nls_charset12.jar), as follows:
If you are using the Oracle JDBC Thick (OCI) driver, then the version of the JDBC files must exactly match that of the database.
If you are using the Oracle JDBC Thin (Pure Java) driver, then you should use the JDBC files from Oracle9i Release 2, 9.2.0.2 or higher.
Ensure that sqlplus is included in the PATH variable.
Run Oracle_home\bibeans\bin\bi_installcatauto.bat on Windows or Oracle_home/bibeans/bin/bi_installcatauto.csh on UNIX as follows:
bi_installcatauto host_name port_id sid
Where host_name is the name of the host machine, port_id is the port identifier, and Sid is the identifier of the database instance. For example :
bi_installcatauto sun-server 1521 orcl
When prompted, enter the password for the user SYSTEM. (If you do not know the password, then ask your DBA.) When you see a warning that the BI Beans Catalog is about to be overwritten, press Y to continue. The script creates a user named BIBCAT, with default tablespace USERS, and temporary tablespace TEMP.
Note: BIBCAT is an application user, as well as the Catalog schema owner. The user name is case sensitive. Application user names are used when running the BI Beans Catalog Explorer. You should also make note of the user name now, because you will need it later when you are developing applications with JDeveloper.
As the script runs, error messages are written to the console. Some error messages occur when database objects that do not exist are dropped; you can ignore such messages. However, if there are other error messages, then review the errors and take appropriate action.
At these last two steps, be very careful with those environment variables (especially the JDBC_CLASSPATH - Windows example -- If the Oracle Home directory is d:\oracle9, then you enter the following: JDBC_CLASSPATH=d:\oracle9\jdbc\lib\classes12.jar;d:\oracle9\jdbc\lib\nls_charset12.jar)
16. after all this, break your keyboard, cause it's still not working :))
17. this I don;t guarantee that will also work for you, but for me, at the end of almost 24 hrs of "installing" finally gave some results.
open sqlplus /nolog
connect / as sysdba
@%Oracle_home%\cwmlite\admin\amdpatch.sql
@%Oracle_home%\cwmlite\admin\postamd.sql
@%Oracle_home%\olap\admin\olap.sql
I think you should also run @%Oracle_home%\olap\admin\olapapi.sql but when I noticed that something finally worked I was too afraid to try anything else.
Here's what
bi_checkconfig.bat -h ana -po 1521 -sid proiect -u bibdemo -p bibdemo -q
returned:
BI Beans Diagnostics(v1.0.2.0) 2/28/05
===============================================================================
JDEV_ORACLE_HOME .......................... = E:\OraDS
JAVA_HOME ................................. = E:\OraDS\jdk
JDeveloper version ........................ = 9.0.4.1.1.1436
BI Beans release description .............. = BI Beans 9.0.4 Production Release
BI Beans component number ................. = 9.0.4.23.0
BI Beans internal version ................. = 2.7.5.32
Connect to database ....................... = Successful
JDBC driver version ....................... = 9.2.0.4.0
JDBC JAR file location .................... = E:\OraDS\jdev\lib\patches
Database version .......................... = 9.2.0.6.0
OLAP Catalog version ...................... = 9.2.0.1.0
OLAP AW Engine version .................... = 9.2.0.1.0
OLAP API Server version ................... = 9.2.0.1.0
BI Beans Catalog version .................. = N/A; not installed in bibdemo
OLAP API JAR file version ................. = 9.2
OLAP API JAR file location ................ = E:\OraDS\jdev\lib\ext
Load OLAP API metadata .................... = Successful
Number of metadata folders ................ = 2
Number of metadata measures ............... = 12
Number of metadata dimensions ............. = 8
Testing sample query for measures and dimensions
(S=Schema, C=Cube, M=Measure, D=Dimension)
1/21) Measure Budget ................... = Successful
S=BIBDEMO, C=BIBDEMO_BUDGET_CUBE, M=BUDGET
2/21) Measure Actual ................... = Successful
S=BIBDEMO, C=BIBDEMO_ACTUAL_CUBE, M=ACTUAL
3/21) Measure Close Price .............. = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_CLOSE
4/21) Measure Open Price ............... = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_OPEN
5/21) Measure Low Price ................ = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_LOW
6/21) Measure High Price ............... = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_HIGH
7/21) Measure Stock Volume ............. = Successful
S=BIBDEMO, C=BIBDEMO_STKPRICE_CUBE, M=STKPRICE_VOLUME
8/21) Dimension Division ............... = Successful
S=BIBDEMO, D=DIVISION
9/21) Dimension Line Items ............. = Successful
S=BIBDEMO, D=LINE
10/21) Dimension Time ................... = Successful
S=BIBDEMO, D=TIME
11/21) Dimension Day .................... = Successful
S=BIBDEMO, D=DAY
12/21) Dimension Stock .................. = Successful
S=BIBDEMO, D=STOCK
13/21) Measure Costs .................... = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.COSTS
14/21) Measure Promotion ................ = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.PROMO
15/21) Measure Quota .................... = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.QUOTA
16/21) Measure Units .................... = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.UNITS
17/21) Measure Sales .................... = Successful
S=BIBDEMO, C=ANALYTIC_CUBE, M=F.SALES
18/21) Dimension Channel ................ = Successful
S=BIBDEMO, D=CHANNEL
19/21) Dimension Geography .............. = Successful
S=BIBDEMO, D=GEOGRAPHY
20/21) Dimension Product ................ = Successful
S=BIBDEMO, D=PRODUCT
21/21) Dimension Time ................... = Successful
S=BIBDEMO, D=TIME
Metadata output location .................. = E:\OraDS\bibeans\bi_checkconfig\bi
_metadata.txt
To interpret this output, see the "Displaying Information about your Oracle9i Bu
siness Intelligence Beans Client Configuration" technical note, whose file name
is bi_checkconfig_tn.html
These diagnostics are captured in: E:\OraDS\bibeans\bi_checkconfig\bi_checkconfi
g.xml
so, is this ok???????
should i do anything else?????????

Answer 1

Hi..
Even I tried installing patch 9.2.0.6. much much similar to the way you tried except for the last two post installation patches you mentioned I didnt run it.
I didnt understnd what the problem is but when I open sqlplus I still see it as 9.2.0.1.
Can anyone suggest me how to correct it or is the way I installed is wrong?
A quick answer would be the biggest favour for me
thanks in advance