The procedure to upload schema to the Database

The procedure to upload a schema to the Database:

Create user :

SQL> conn system/password@ora10g

Connected.

SQL> create user s_nq_sched

  2  identified by password

  3  default tablespace users

  4  temporary tablespace temp

/

Grant the following to the User:

SQL> grant connect

  2  ,     create table

  3  ,     create view

  4  ,     create procedure

  5  to    s_nq_sched

/

Connect to the user and copy the schema:

SQL> conn s_nq_sched/password@ora10g

Connected.

SQL> @c:\SiebelAnalytics\Schema\SAJobs.Oracle.sql

 

Installing ODBC Drivers

Installing ODBC Drivers

1. Download client32.zip.
2. Unzip client32.zip into a folder. Run Setup.exe from the folder.

3. Click Next or Yes on the screen until you get to the Interbase component selection screen. Here you need to uncheck all options except for the last option: OBDC driver.

4. The destination folder should be the Interbase folder you already have set up in Quantum. This is usually either c:\quantum\interbase or c:\program files\interbase corporation\interbase. Click Install.
5. When a message appears saying that the installation was successful, click Finish.
6. Go to Start -> Settings -> Control Panel. Open Administrative Tools.

7. Open Data Sources (ODBC).

8. In the ODBC Data Source Administrator window, click the User DSN tab, and the click Add... to create a new data source.

9. Select INTERSOLV InterBase ODBC Driver (*.gdb) from the list and click Finish.

10. In the ODBC InterBase Driver Setup screen, click the General tab. Then enter the name for your data source. This should be something like "Quantum Database", or some other descriptive name for the connection. In the Database Name field, enter the complete path to the Quantum database. This should include server IP address, the path on the server and the file name with extension. Use the form: IPaddress:drive:\path\quantum.gdb.

11. Click OK. This data source should now appear in the User Data Sources section of the ODBC Data Source Administrator. Click OK to close this window.

To use with Microsoft Excel (97, 2000, XP):

Note: you might need the Excel or MS Office CD to perform these operations. If at any point during this time you are prompted to install from the CD, insert the CD and follow on screen instructions. Please refer to Excel documentation for more information.

The following steps should be performed only on a machine that has ODBC drivers installed (see steps 1-11 above).

1. Start Excel. Go to the Data drop down menu and select Get External Data. Then select New Database Query.

2. Select the Data Source you created above and click OK.

3. Enter your user name and password and click OK.

4. When the Query Wizard window appears, you are connected to the Quantum database. At this point you may select tables and/or fields to include in your query. Please refer to the Quantum data dictionary for information regarding the tables and to MS Query documentation for assistance with using Query.

How To Start / Stop An OBIEE 11g (11.1.1.x) Unix / Linux Environment Via Command-line

How To Start / Stop An OBIEE 11g (11.1.1.x) Unix / Linux Environment Via Command-line

Starting the environment via command-line:

The high-level manual steps are:

• Set your environment
• Start WLS Admin Server in the background
• Start WLS NodeManager
• Start WLS Managed Server
• Start Oracle Instance

Note: init.d boot time startup scripts are not covered here.  These examples are from Oracle Enterprise Linux 5

1. Set your environment (manually or via script). 

Note: You may use the standard environment scripts (commEnv.sh, setDomainEnv.sh, etc) ; however, these are the minimal variables necessary for these examples

MW_HOME=/[path]/[obiee11g_middleware_home]; export MW_HOME
DOMAIN_HOME=/$MW_HOME/user_projects/domains/bifoundation_domain; export DOMAIN_HOME
WL_HOME=$MW_HOME/wlserver_10.3; export WL_HOME
ORACLE_HOME=$MW_HOME/Oracle_BI1; export ORACLE_HOME
ORACLE_INSTANCE=$MW_HOME/instances/instance1; export ORACLE_INSTANCE
#
# You may also want to set your PATH environment to avoid having to use
# paths in the commands
#
PATH=$WL_HOME/server/bin:$DOMAIN_HOME/bin:$ORACLE_INSTANCE/bin:$ORACLE_HOME/OPatch:$PATH; export PATH

2. Start the WebLogic (WLS) Administration Server in the background

Note:  For username and password, you can:

• pass username/pwd in the command line, 
• use the boot.properties file for an encrypted username/password
• set as environment variables - WLS_USER / WLS_PW,
• or pass WLS_USER /WLS_PW in the start scripts. 
  
  Please see the Oracle WebLogic documentation to determine what meets your need. 
  
  In these examples, you can name the logs whatever you desire.

Execute:

nohup sh $DOMAIN_HOME/bin/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=[_your_password_] > wls_start.log &

Next, tail the log to determine if the server started completely.

execute:
tail -f [log name]

wait until you see:
<WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

 there should be no further lines after this. If successful,  proceed to step 3. If errors, correct them and restart.

Note: This takes some time.  The terms "takes some time", "starts fast", "starts slow", "takes xx amount of time" are all relative terms depending upon resources in your environment.

3. Start Node Manager 
   
   

Note: In this example, the username and password are embedded in script via WLS_USER and WLS_PW.  If you need another method or a more secure method, like a boot.properties  file, then please see:
Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server 11g Release 1 (10.3.1)

Execute:

nohup sh  $WL_HOME/server/bin/startNodeManager.sh > startNodeManager.log &

Next, tail the log to determine if the server started completely. 
tail -f [log name]


Look for <INFO> <Secure socket listener started on port 9556>

Note: starts fast

4. Start the OBI Managed Server (bi_server1 -- default  - java bits)

Note: This can be started via Fusion Middleware Control  or WebLogic Administration Console as well. For this example, modify WLS_USER and WLS_PW in the startManagedWebLogic.sh script to the values chosen during installation. You can set ADMIN_URL in the environment, in the script or pass on the command-line. In this example, it is passed on the command-line.

Execute:

nohup sh $DOMAIN_HOME/bin/startManagedWebLogic.sh bi_server1 http://server.domain:7001 > start_bi_server1.log &

Next, tail the log to determine if the server started completely. 
tail -f [log name]


look for "Server started in RUNNING mode: 
<Mon D, YYYY H:MM:SS PM EDT> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "wls_ods1" for domain "IDMDomain" running in Production Mode>
<Mon D, YYYY H:MM:SS PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Mon D, YYYY H:MM:SS PM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode

Note: takes about 30 seconds depending upon your environment. At this point, you could start any other servers that you have configured in the same manner. For example, WLS_DISCO, WLS_PORTAL.

5. Start the OBIEE System Components ( BI Servers -- c++ bits)

$ORACLE_INSTANCE/bin/opmnctl startall

Next, execute:  opmnctl status or opmnctl status -l (lower case L) to ensure the processes are started properly/completely. 


The output will look similar to this:

$ORACLE_INSTANCE/bin/opmnctl status -l

Processes in Instance: instance1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component | process-type | pid | status | uid | memused | uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
coreapplication_obiccs1 | OracleBIClusterCo~ | 11741 | Alive | 70916792 | 55188 | 0:01:01 | N/A
coreapplication_obisch1 | OracleBIScheduler~ | 11740 | Alive | 70916789 | 122388 | 0:01:01 | N/A
coreapplication_obijh1 | OracleBIJavaHostC~ | 11739 | Alive | 70916790 | 1186088 | 0:01:01 | javahost:9810
coreapplication_obips1 | OracleBIPresentat~ | 11742 | Alive | 70916791 | 261576 | 0:01:01 | N/A
coreapplication_obis1 | OracleBIServerCom~ | 11738 | Alive | 70916788 | 150904 | 0:01:01 | N/A

Stopping the enviroment cleanly via the command-line:

Reverse the steps above with the following commands:

Note: You can look inside the respective scripts or the documentation for alternative or more secure methods. You can also kill the processes, but you may risk corruption.

1. Stop the Oracle Instance  
   $ORACLE_INSTANCE/bin/opmnctl stopall
2. Stop the OBIEE Managed Server (bi_server1) 
   $DOMAIN_HOME/bin/stopManagedWebLogic.sh bi_server1 t3://host.domain:7001 username password
   
   If running other managed servers, then stop them in the same manner.
3. Stop the the WebLogic (WLS) Administration Server 
   $DOMAIN_HOME/bin/stopWebLogic.sh username password t3://host.domain:7001
4. At this point, since the node manager was started in another shell in the background, then you will need to kill the JVM process that the node manager is running under. There should be no risk of corruption at this point since everything is already shutdown.  If you had started the node manager in a shell (and not in the background), then you could just close the shell.
   
   You can use the command ps -ef | grep [os user] to check for running processes under the specified user and then kill the JVM process with kill -9 [PID] (where PID is the process id of the running JVM)

Installation Informatica Powercenter 9

Installation Informatica Powercenter 9.0.1 on Oracle Enterprise Linux 5.6

Ingredients:

Program	Version	Filename
Oracle Express 11G	11.2.0	oracle-xe-11.2.0-0.5.x86_64.rpm
SQL Developer	3.0	sqldeveloper-3.0.04.34-1.noarch.rpm
Informatica Powercenter	9.0.1	901HF2_Server_Installer_linux-x64.tar
Oracle Enterprise Linux	5.6	Enterprise-R5-U6-Server-x86_64-dvd.iso

For this demonstration Oracle Enterprise Linux (a.k.a. “Unbreakable Linux”) was used. Installed in a virtual environment with 1,5GB RAM and a 25GB harddisk.

In order to get Informatica Powercenter up and running on a server, you would typically need a database first. Otherwise it would be hard for the application to store it’s meta-data anywhere. Since this is an example, a not so large database was used; Oracle Express 11G.

Installation Oracle Express 11G
It’s important to check the free space in our memory first. Oracle XE needs around 4GB of swap memory for its installation. So let’s open a command line and check the memory using the commandfree

[root@fusionapps install]# free
total used free shared buffers cached
Mem: 1531688 1441668 90020 0 16128 1175480
-/+ buffers/cache: 250060 1281628
Swap: 2064376 0 2064376

Installation of the Operating System was with almost all default settings. This also means the amount of swap memory wasn’t changed. This needs to be raised before starting the installer package.

[root@fusionapps install]# dd if=/dev/zero of=/swapfile bs=1024 count=2048000
2048000+0 records in
2048000+0 records out
2097152000 bytes (2.1 GB) copied, 28.0329 seconds, 74.8 MB/s

[root@fusionapps install]# /sbin/mkswap /swapfile
Setting up swapspace version 1, size = 2097147 kB
[root@fusionapps install]# /sbin/swapon /swapfile
[root@fusionapps install]# free
total used free shared buffers cached
Mem: 1531688 1441404 90284 0 16416 1174944
-/+ buffers/cache: 250044 1281644
Swap: 4112368 0 4112368

This should do it, now onto the installation of the database itself. Locate the package and run it withrpm -i oracle-xe-11.2.0-0.5.x86_64.rpm. This should result into the following:

[root@fusionapps install]# rpm -i oracle-xe-11.2.0-0.5.x86_64.rpm
Executing post-install steps…

You must run ‘/etc/init.d/oracle-xe configure’ as the root user to configure the database.

Fine, looks alright even though you can’t see what it has done. Basically your database software is ready to be used, yet no database yet. So let’s do what the package told us to do, execute the command /etc/init.d/oracle-xe configure.

[root@fusionapps admin]# /etc/init.d/oracle-xe configure

Oracle Database 11g Express Edition Configuration
————————————————-
This will configure on-boot properties of Oracle Database 11g Express Edition. The following questions will determine whether the database should be starting upon system boot, the ports it will use, and the passwords that will be used for database accounts. Press to accept the defaults.
Ctrl-C will abort.

Specify the HTTP port that will be used for Oracle Application Express [8080]:

Specify a port that will be used for the database listener [1521]:

Specify a password to be used for database accounts. Note that the same
password will be used for SYS and SYSTEM. Oracle recommends the use of
different passwords for each database account. This can be done after
initial configuration:
Confirm the password:

Do you want Oracle Database 11g Express Edition to be started on boot (y/n) [y]:

Starting Oracle Net Listener…Done
Configuring database…Done
Starting Oracle Database 11g Express Edition instance…Done
Installation completed successfully.

At each question the answer is to hit the enter button so that the default values stay as they are. Only exception to this is where you need to enter a password for your database.
Now to test if a connection can be made to the database. Look at the top left menu and selectApplications > Oracle Database 11g Express Edition > Run SQL Command Line and review the following:

SQL> connect system/xe@xe
Connected.

SQL> select name from v$database;
NAME
—-
XE

SQL>

This looks right, the database is up and running. The installation of SQLDeveloper can begin. Note that this is not really needed, but some people prefer a more graphical way of doing their queries and other database tasks.

Installation SQLDeveloper
This installation is pretty straight forward. Look up the package and run the following from the command line: rpm –i sqldeveloper-3.0.04.34-1.noarch.rpm
This should give you:

[root@fusionapps install]# rpm -i sqldeveloper-3.0.04.34-1.noarch.rpm
[root@fusionapps install]#

Now when you look in the Applications menu, there should be a menu item called SQL Developer under the Programming submenu.

Installation Powercenter 9.0.1
In order to begin the installation of Powercenter there are some prerequisites that need to be met first:

Going through these ingredients one by one;

1.                4GB disk space, check

2.                We have an Oracle database, check

3.                Database user account is not there yet, to do

4.                Valid license key, Oracle provides one with the download from eDelivery. This isn’t meant for production purposes, but it’s very useful when trying installations like these, check

5.                Database user for domain configuration can be the same as point 4, to do

6.                Port numbers is useful to align for yourself, but since this is a totally new system we’ll use the default ports Powercenter issues (i.e. 6005-6007 and some others4GB RAM, not needed at all. For this installation a virtual machine was used with 1,5GB of RAM and it had no problem installing Powercenter at all, so check

Conclusion of the ingredients list is one more task that isn’t done yet, create a database user that Powercenter can use to do its work.

SQL> create user informatica identified by password;
User created.

SQL> grant all privileges to informatica;
Grant succeeded.

SQL>

With above statements this final task is complete as well. So with all the boxes checked the installation of Powercenter can begin.
Lookup your downloaded Powercenter installation file (901HF2_Server_Installer_linux-x64.tar) and untar it at a destination of your choice. Then it’s just a case of starting the install.sh file.

[admin@fusionappsIPC901]$ . install.sh
OS detected is Linux
unjar task is in progress………….
unjar of ESD completed…..
Do you want to continue installation (y/n) ?

Unjarring the files will take a while, obviously depending on your system specifications. When the installer asks to continue, the answer is y for yes.

Starting installation …

\***************************************************************************
\* Welcome to the Informatica 9.0.1 HotFix 2 Server Installer. *
\***************************************************************************

To verify whether a machine meets the system requirements for an Informatica installation, run the Pre-Installation System Check Tool (i9Pi) before you start the installation process. You can find the i9Pi tool in the following directory: /i9Pi

Before you continue, read the 9.0.1 HotFix 2 Installation Guide and Release Notes.
You can find the 9.0.1 HotFix 2 documentation in the Documentation Center at http://my.informatica.com Configure the LANG and LC_ALL variables to generate appropriate code pages and create and connect to repositories and Repository Services.
Do you want to continue? (Y/N)

A lot of information, so it’s wise to read them before continuing. At the end it says not to forget to set some variables. This is wise to check with the export command. When all is well, we can move on by typing y for yes again.

Installer requires operating system Linux version 2.6 and later.
Current operating system Linux version 2.6.
Current operating system meets minimum requirements.

Select a choice :
1. Install Informatica 9.0.1 with Hot Fix 2 or Upgrade from a previous version of Informatica to Informatica 9.0.1 with Hot Fix 2
2. Apply Informatica 9.0.1 Hot Fix 2 to existing 9.0.1 install.
Enter the choice(1 or 2):

Now we need to choose the installation that we want. In this case option 1 is the way to go, nothing is installed yet so no need to apply just a hotfix.

———————————————————–
Checking for existing 9.0.1 HotFix 2 product installation.
Select (G)UI mode (needs X Window support) or (C)onsole mode (G/C):

Next question is the type of installer that we want to use. Let’s be lazy and use a graphical interface (ideal for cheering up this bunch of text with some screenshots).
Launching installer in GUI mode …
Preparing to install…
Extracting the JRE from the installer archive…
Unpacking the JRE…
Extracting the installation resources from the installer archive…
Configuring the installer for this system’s environment…

Launching installer…

Preparing SILENT Mode Installation…

===========================================================================
Informatica 9.0.1 Services HotFix2 (created with InstallAnywhere)
—————————————————————————

After choosing G for GUI mode the installer will start it up with the above information. After this is done, a window opens and the graphical installer is launched.

First window let’s you choose the type of installation. Funny enough we already gave an answer to this question, but there’s no harm in answering again.

The list of prerequisites is next. You’ve seen this list before (scroll up if you missed it) and all should be good at this point. So onto the next one.

This is where we actually need to do something; showing the installer where our license key is located and where Powercenter should be installed.

The installer then gives you a small summary of what was chosen. If this looks good then the actual installation can begin by pressing the Install button.

Configuration is the next task the installer wants to do. For this fresh installation we’ll be making a brand new domain. If for any reason there is a need to join an already existing domain then the second option is the way to go.

As per default the HTTPS option is enabled. No reason to untick it if you don’t have or don’t want to add a legitimate certificate. The installer can make a dummy one for you. Not only in this case, but also with a production machine this would be harmless. Simple reason is that Powercenter is installed based on the hostname. So if you’re not on that hostname, you can’t login to the administration console. This basically means that by default you can’t use the administration console outside of the server. This can be configured however, so when you decide to do that, it would be wise to install legitimate certificates.

Next the installer wants to know where to install all its information. This is where the database user informatica comes in. And since the database is on the same machine as Powercenter will be, it’s no problem using localhost as the address for the database.

By using the button Test connection the installer enables you to check if you didn’t make any typo’s:

Final window before the Powercenter installation is properly configured is where information is requested on the domain that needs to be created.

And if all goes well, the last screen you’ll see is the one below stating this installation was a success.

And there you go, a freshly installed Informatica Powercenter 9.0.1. Ready to be decorated with repositories and to be used with (for example) Oracle Fusion Applications feeding Oracle BI components.

OBIEE 11G Logs and Configuration Files

Troubleshooting Usage	Log Name	Log Location	Location Example	Increase Log Level	Log configuration file
Install\De-install\Patch
	Examples: deinstall2010-08-15_09-01-33PM.out deinstall2010-08-15_09-01-33PM.log installProfile2010-08-15_09-01-33PM.log oraInstall2010-08-15_09-01-33PM.out oraInstall2010-08-19_01-21-49AM.err OPatch2010-08-19_02-15-05-AM.log 2010-08-19_01-21-49AM.log installProfile2010-08-19_01-21-49AM.log	■ Linux and UNIX: USER_HOME/oraInventory/logs/ ■ Windows: C:\Program Files\Oracle\Inventory\logs\	C:\Program Files\Oracle\Inventory\logs	Q: Is this possible ?	?
Startup\Shutdown\Execution
WLS Admin Server	AdminServer.log bifoundation_domain.log AdminServer-diagnostic.log(BI JEE log (Action Services and Security Services), - review in FMC) access.log logs\bipublisher \bipublisher.log  ?????	<Middleware_HOME>\user_projects\domains\bifoundation_domain\servers\AdminServer\logs	C:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\AdminServer\logs	In WLS Console > biFoundation_domain > servers > AdminServer Logging Tab has a General and an HTTP sub-tab General (general settings for logs for this server) By default all messages are published By default all messages go to the log file.	?
WLS Managed Server	bi_server1.log bi_server1.out bi_server1.out00001 etc bi_server1-diagnostic.log (BI JEE log (Action Services and Security Services), - review in FMC) access.log logs\bipublisher \bipublisher.log  ?????	<Middleware_HOME>\user_projects\domains\bifoundation_domain\servers\bi_server1\logs	C:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\bi_server1\logs	biFoundation_domain > servers > bi_server1 Logging Tab has a General and an HTTP sub-tab General sub-tab (general settings for logs for this server) By default all messages are published By default all messages go to the log file.	?
BI System Components (BI instance)
OracleBIServerComponent	nqserver.log Nqquery.log Administrator_NQSAdminTool.log Administrator_nQUDMLExec.log (For detailed info  : See System Administrator's Guide for Oracle Business Intelligence Enterprise Edition, 8.2 Understanding Diagnostic Log and Log Configuration Files)	<ORACLE_INSTANCE>\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1\	C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1\	Use FMC Diagnostics tab > Log Configuration to set a higher “Log Level” Log Levels ■ Incident Error option ■ Error option ■ Warning option ■ Notification option ■ Trace option such as set Trace to “FINEST” (performance impact!) For nqquery.log, set level 0 thru 5 in BI Admin Tool > Manage Security for each user	ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBIServerComponent\coreapplication_obis1\logconfig.xml
OracleBIPresentationServicesComponent	sawlog0.log webcatupgrade0.log \catalogcrawler\ sawcatalogcrawlerlogsys0.log	<ORACLE_INSTANCE>\diagnostics\logs\ OracleBIPresentationServicesComponent \coreapplication_obips1\	C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1\	As above	ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBIPresentationServicesComponent\coreapplication_ obips1\instanceconfig.xml
OracleBISchedulerComponent	nqscheduler-<n>.log	<ORACLE_INSTANCE>\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1	C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1		ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBISchedulerComponent\coreapplication_obisch1\instanceconfig.xml
OracleBIJavaHostComponent	Jh.log Jh-n.log	<ORACLE_INSTANCE>\diagnostics\logs\ OracleBIJavaHostComponent\coreapplication_obijh1\	C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBIJavaHostComponent\coreapplication_obijh1\	As above	ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBIJavaHostComponent\coreapplication_obijh1\logging_config.xml
OracleBIClusterControllerComponent	Nqcluster-<n>.log	<ORACLE_INSTANCE>\diagnostics\logs\ OracleBIClusterControllerComponent\coreapplication_obiccs1\	C:\OBIEE11G\instances\instance2\diagnostics\logs\OracleBIClusterControllerComponent\coreapplication_obiccs1\	As above	ORACLE_INSTANCE\config\component_type\bi_component_name \OracleBIClusterControllerComponent\coreapplication_obiccs1\ccslogconfig.xml
OPMN	Debug.log Opmn.log Service.log etc		C:\OBIEE11G\instances\instance2\diagnostics\logs\OPMN\opmn	As above	ORACLE_INSTANCE\config\component_type\bi_component_name\ \OPMN\opmn\opmn.xml
Troubleshooting Java Components
As above plus
EmbeddedLDAP (can be used in conjunction with the access.logs, as above	EmbeddedLDAP.log EmbeddedLDAPAccess.log	DOMAIN_HOME/servers/server_name/data/ldap/log/EmbeddedLDAP.log DOMAIN_HOME/servers/server_name/data/ldap/log/	C:\OBIEE11G\user_projects\domains\bifoundation_domain\servers\bi_server1\data\ldap\log\EmbeddedLDAP*.log	?	?
Miscellaneous
Repository log	<Repository Name> .rpd.log	<ORACLE_INSTANCE>\OracleBIServerComponent\coreapplication_obis1\repository\	C:\OBIEE11G\instances\instance2\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository\SampleAppLite.rpd.Log	?	?
Upgrade	ua<timestamp>.log	BI_ORACLE_HOME\upgrade\logs		?	?
Usage Tracking (Only if redirected to logs)	NQAcct.yyyymmdd.hhmmss.log	STORAGE_DIRECTORY parameter in the Usage Tracking section of the NQSConfig.INI file determines the location of usage tracking log files		?	?
BI Agent Log	Agent-JobID-InstanceID.xxx	The default location for log files is the Log directory in the Oracle Business Intelligence installation directory on the computer where the Oracle BI Scheduler is installed.		?	?

Configuration Files

Source: Oracle® Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition > Where are Configuration Files Located?

Oracle BI Server

NQSConfig.INI

logconfig.xml

ORACLE_INSTANCE\config\OracleBIServerComponent\coreapplication_obisn

For example:

\instances\instance1\config\OracleBIServerComponent\coreapplication_obis1

Note: Although DBFeatures.ini is also located in this directory, do not edit this file directly. See Oracle Fusion Middleware

Metadata Repository Builder's Guide for Oracle Business Intelligence  Enterprise Edition for information about how to edit features for a

database.

Oracle BI Presentation Services

instanceconfig.xml  ORACLE_INSTANCE\config\OracleBIPresentationServicesComponent\coreapplication_obipsn

For example:

\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1

Note: Do not add elements to the instanceconfig.xml file unless you are overriding the stated default values. Override only those

settings that are necessary for configuring the system to meet the needs of your organization.

Cluster Controller

NQClusterConfig.INI

ccslogging.xml

ORACLE_INSTANCE\config\OracleBIApplication\coreapplication

For example:

\instances\instance1\config\OracleBIApplication\coreapplication

Oracle BI Scheduler

instanceconfig.xml

ccslogging.xml

(for Cluster Controller)

ORACLE_INSTANCE\config\OracleBISchedulerComponent\coreapplicati on_obischn

For example:

\instances\instance1\config\OracleBISchedulerComponent\coreapplication_obisch1

JavaHost

config.xml

logging_config.xml

ORACLE_INSTANCE\config\OracleBIJavaHostComponent\coreapplication_obijhn

For example:

\instances\instance1\config\OracleBIJavaHostComponent\coreapplication_obijh1

Oracle BI Presentation Services Plug-in

bridgeconfig.properties

MW_HOME\user_projects\domains\domain_name\config\fmwconfig\biinstances\coreapplication

For example:

mw_home\user_projects\domains\bifoundation_domain\config\fmwconfig\biinstances\coreapplication