INSTALLATION DOCUMENTS BY RAVI

Wednesday, December 4, 2019

How to Connect to the Oracle Analytics Cloud (OAC) RPD using Client Admintool with SSL port


Connect to OAC via the "In the Cloud" option:
Launch the Oracle BI Administration Tool
Choose File > Open > In the Cloud





















Define the parameters for your OAC instance:
Username: admin
Password: ***********
Cloud: bootstrap
Host Name: test.oraclecloud.com
Port Number: 443
SSL: Check ON
Trust Store: <OAC Client Home>\oracle_common\jdk\jre\lib\Security\cacerts
Password: changeit (This is the default password for cacerts)


























Click on open




















How to find WiFi password using windows command prompt

Note: This will show the passwords of wifi networks which you connected at least ones.

Open the command prompt as Administrator



















Enter the below command to list the wifi profiles you connected so far
netsh wlan show profile




















Enter the below command to see the password of the wife network
netsh wlan show profile wifi-name key=clear



Saturday, July 27, 2019

Installing and Configuring Oracle Analytics Cloud Data Sync


Installing Data Sync
Data Sync stores sensitive information, including connection information to our on-premises databases. It is recommended that we only install Data Sync in protected environments where the operating system and file system privileges are tightly controlled.
Prerequisite:
Install Java Development Kit (JDK) 1.7 or later
Note:
Data Sync doesn’t work with Java Runtime Environment (JRE). We must install JDK.
Steps for installing and configuring Data Sync:
Download Data Sync from Oracle Technology Network:
Unzip BICSDataSync_Vx_x.Zip to a directory with no spaces in its name.




















Setting JAVA_HOME:
Open config.bat (Windows) or config.sh (Linux or Unix).
Replace @JAVA_HOME with the directory where JDK is installed.





















Copy any database-specific JDBC drivers that we need to Data Sync’s \lib directory.
Data Sync installs Oracle JDBC driver 11.2.x. If we want to connect to a different database (for example, Microsoft SQL Server or DB2) or if you want to use a different Oracle driver from the default version, obtain and manually copy the required files to the \lib directory



















Starting Data Sync for the First Time:
The first time we start Data Sync, you’ll be asked to give your Data Sync repository a name and provide a password.
To Start Data Sync. Run datasync.bat (on Windows) or datasync.sh (on Linux/UNIX) from the directory where you installed Data Sync.




















Open the command prompt and run the datasync.bat file as below
















Click on Next



















Select Configure a new environment and click on Next



















Provide repository name and click on Next



















Provide the password and click on Next



















After configuration got completed click on Finish



















To start Data Sync server run startserver.bat as below





























To open Data Sync Tool run datasyncClient.bat




















Provide login password which we were given while configuration and click on Login



















Select Create a New Project
Provide a name for the project and click on ok



















Click on Ok
















To stop Data Sync Server run stopserver.bat file as below





























Tuesday, July 23, 2019

Connecting Microsoft SQL Server using Oracle SQL developer


We can connect Microsoft SQL server using oracle SQL developer by following the steps below.



Download “jTDS-SQL Server and Sybase JDBC driver”.





















Open SQL developer



















Click on Tools and then click on Preferences



















Under Database Click on Third Party JDBC Driver



















Add the downloaded SQL server JDBC driver and click on ok


















Try to create a new connection, we will see SQL Server option now.

Select SQL Server and provide the connection details and Click on Test.
We will get a Success status.
























Sunday, July 21, 2019

Error in invoking target 'agent nmb nmo nmhs' of makefile


Error in invoking target 'agent nmb nmo nmhs' of makefile
















INFO: Exception thrown from action: make
Exception Name: MakefileException
Exception String: Error in invoking target 'agent nmb nmo nmhs' of makefile '/u01/app/oracle/product/11.2.0/dbhome_1/sysman/lib/ins_emagent.mk'. See '/u01/app/oraInventory/logs/installActions2019-06-17_02-10-30AM.log' for details.
Exception Severity: 1

SOLUTION
The solution is to add “-lnnz11” to the end of the ins_emagent.mk
Edit $ORACLE_HOME/sysman/lib/ins_emagent.mk, search for the line
$(MK_EMAGENT_NMECTL)
 Replace the line with
$(MK_EMAGENT_NMECTL) -lnnz11
Then click “Retry” button to continue.










































Customizing Logo OBIEE 12.2.1.4


Form OBIEE 12.2.1.3 and later for customizing logo under Administration, Theme Management option ids provided
Steps for customizing Logo:
Login to Analytica page and click on Administration





















Under Theme Management click on Manage Themes









































Now we are going to change the default logo from oracle to google.
Note:
Image name must be saved without any special characters
Image size must not exceed Pixels Horizontal: 130 and Vertical: 28
Example image file:



Provide Theme Name
Select Logo and upload the image file we want to use as logo
Provide Header Title
Check the box for Active
Click on Save




















We will get a successful message
Click on Ok




















Reload the page
Now we will able to see Custom Logo and Title




















OBIEE 12c Start Script Fails to Connect to the Node Manager with Error General SSLEngine Problem


After configuring SSL with Custom Identity and Trust Keystores and when we try to start the servers getting the below error


























Resolution:
To resolve this Invoke WLST with additional Java parameters that explicitly identify the Custom Trust KeyStore, as below
Backup the ORACLE_HOME/oracle_common/common/bin/wlst_internal.sh file







Edit the wlst_internal.sh file, add the Java parameters (either before or after the ${JVM_ARGS} entry)
From:  eval '"${JAVA_HOME}/bin/java"' ${JVM_ARGS} weblogic.WLST '"$@"'
To:

eval '"${JAVA_HOME}/bin/java"' ${JVM_ARGS} -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.CustomTrustKeyStoreType="JKS" -Dweblogic.security.TrustKeyStore=CustomTrust -Dweblogic.security.CustomTrustKeyStoreFileName="/u01/app/oracle/keystores/keystore.jks" weblogic.WLST '"$@"'






















Save and close the file.
Try to restart the servers again

































Sunday, June 30, 2019

Customizing logo OBIEE 12c lightweight login page


With OBIEE 12.2.1.4.0 there is, by default, a new login page called “lightweight SSO”.
It has a different style when compared to the “old” classical login page
By deploying a custom “oracle_logo.png” it will not affect the new login page.





















But after login to the page we were able to see the custom logo we deployed.





















If we inspect the page we didn’t find the oracle_logo.png and we can observer that it is using a different font as below “vafont”





















If we disable the font we can observer that “ORACLE” is replaced by a rectangle





















Workaround:
By editing the CSS file “loginhelper.css” we can customize the logo as below
Getting the logo URL:
Login to analytics page
Right click on logo and click on “View image info”





















Copy the image url

























/analytics/res/v-0gVQmmIfY4w/s_Alta/master/oracle_logo.png




Modify the file “loginhelper.css “ under the location /u01/app/oracle/middleware/user_projects/domains/bi/servers/bi_server1/tmp/_WL_user/bi-security-login/7iuedy/war/css as below
Remove the line “font-family: 'vafont';” under bitech-logo and add the image url to content under bitech-logo::before as below






















Login to EM console and restart the components







































Now we are able to see the custom logo





















  Opatch reports 'Cyclic Dependency Detected' error when patching ODI   Issue: When applying a Patch Set Update (PSU) to WebLogic Se...