Retrieve Apps password in R12 or Forgot Apps Password in R12

Retrieve Apps password in R12 or Forgot Apps Password in R12

Steps to retrieve forgotten apps password in R12

Step 1 : login to DB-Node

sqlplus / as sysdba

STEP 2 : Create Function for to decrypt the encrypted password


SQL> create FUNCTION apps.decrypt_pin_func(in_chr_key IN VARCHAR2,in_chr_encrypted_pin IN VARCHAR2)
RETURN VARCHAR2
AS
LANGUAGE JAVA NAME 'oracle.apps.fnd.security.WebSessionManagerProc.decrypt(java.lang.String,java.lang.String) return java.lang.String';
/

Function created.

STEP 3 : (Query for password)


SQL> select ENCRYPTED_FOUNDATION_PASSWORD from apps.fnd_user where USER_NAME='GUEST';


Output

ENCRYPTED_FOUNDATION_PASSWORD
--------------------------------------------------------------------------------
ZG37E123746712BDB2D99E048FE44AE662F2713E2EDB443391BABA0414CADDB7A2E6DD45BBAFA7270A663E5EEBA837F5548A

STEP 4:

SELECT apps.decrypt_pin_func('GUEST/ORACLE','ZG37E123746712BDB2D99E048FE44AE662F2713E2EDB443391BABA0414CADDB7A2E6DD45BBAFA7270A663E5EEBA837F5548A') from dual;




Output

APPS.DECRYPT_PIN_FUNC('GUEST/ORACLE','ZG37E123746712BDB2D99E048FE44AE662F2713E2EDB443391BABA0414CADDB7A2E6DD45BBAFA7270A663E5EEBA837F5548A')
--------------------------------------------------------------------------------
DEMONSTRATE

STEP 5: (Test apps password)

SQL> conn apps/DEMONSTRATE;
Connected.

CHEERS :)

If the Admin Password of an EBS WebLogic Domain is lost or forgotten

As noted earlier, the EBS WebLogic domain uses Node Manager to control startup of the AdminServer and Managed Servers. For the EBS WebLogic domain, the Node Manager and WebLogic AdminServer passwords must be same. If the passwords are different, the AD control scripts will not work properly.

If the AdminServer password has been lost or forgotten, it can be reset by carrying out the following steps on the run file system. As described in the final step, an fs_clone operation should then be performed to synchronize the run and patch file systems.

1. Shut down all running services. Since the AdminServer password is not known, the servers cannot be stopped from the console and so must be killed as follows.
   1. Connect to the Oracle E-Business Suite instance and source the application tier environment file.
   2. Identify the PIDs of Node Manager, AdminServer, and all running Managed Servers:

      $ ps -ef | grep "NodeManager"
      $ ps -ef | grep "weblogic.Name=AdminServer"
      $ ps -ef | grep "weblogic.Name=forms-c4ws_server"
      $ ps -ef | grep "weblogic.Name=forms_server"
      $ ps -ef | grep "weblogic.Name=oafm_server"
      $ ps -ef | grep "weblogic.Name=oacore_server"

   3. Kill all these processes, starting with Node Manager and followed by the Managed Servers.
2. Back up these folders, and then delete them:

   <EBS_DOMAIN_HOME>/security/ DefaultAuthenticatorInit.ldift
   <EBS_DOMAIN_HOME>/servers/<server_name>/data/ldap
   <EBS_DOMAIN_HOME>/servers/<server_name>/security/boot.properties
   <EBS_DOMAIN_HOME>/servers/<server_name>/data/nodemanager/boot.properties
   
   

   Where:
   • <EBS_DOMAIN_HOME> is the absolute path of the EBS WebLogic domain
   • <server_name> is the name of the server directory under <EBS_DOMAIN_HOME>.
   If the password is not reset correctly, the backed up files and folders can be restored.
   Note: For certain servers, the boot.properties file may be present in only one location of the two specified above. In such a case, back it up and then delete it.
3. Set up a new environment to change the WLS AdminServer password.
   1. Start a new session and connect to the Oracle E-Business Suite instance.
   2. Do not source the application tier environment file.
   3. Run the following command to source the WebLogic Server domain environment:

      $ cd <EBS_DOMAIN_HOME>/bin
      $ source setDomainEnv.sh

   4. Run the following commands:

      $ cd <EBS_DOMAIN_HOME>/security
      $ java weblogic.security.utils.AdminAccount <wls_adminuser> <wls_admin_new_password> .

      Where:
      • <wls_adminuser> is the same as the value of context variable s_wls_admin_user
      • <wls_admin_new_password> is the new WLS AdminServer password you wish to set.
      Note: Do not omit the trailing period ('.') in the above command: it is needed to specify the current domain directory.
4. Start AdminServer from the command line. You will be prompted for the WebLogic Server username and password, so that the AdminServer boot.properties file can be generated.
   1. Go to the EBS Domain Home:

      $ cd <EBS_DOMAIN_HOME>

   2. Start AdminServer:

      $ java <s_nm_jvm_startup_properties> -Dweblogic.system.StoreBootIdentity=true -Dweblogic.Name=AdminServer weblogic.Server

      Where:
      • <s_nm_jvm_startup_properties> is the same as the value of context variable ss_nm_jvm_startup_properties
      The above command prompts for the WebLogic Server username and password:

      Enter username to boot WebLogic server:
      Enter password to boot WebLogic server: 

      Provide the same credentials as you provided in Step 3.
5. Change the Node Manager password.
   1. Log in to the WebLogic Administration console.
   2. Click the 'Lock & Edit' button.
   3. In the left panel, click on the EBS Domain link.
   4. Select the 'Security' tab.
   5. Click on the 'Advanced' link.
   6. Edit the 'Node Manager password' field and set it to the new WebLogic Server password. The password should be same as set in Step 3.
   7. Edit the 'Confirm Node Manager Password' field and set it to the new WebLogic Server password. The password should be same as set in Step 3.
   8. Save and activate the changes.
6. The first time, AdminServer has to be stopped from the Admin console. Follow these steps:
   1. Log in to the WebLogic Administration console.
   2. Shut down AdminServer.
7. Set up your environment to start AdminServer again. AdminServer should now be started using the normal AD script, which will also start Node Manager using the new password.
   1. Launch a new session and connect to the Oracle E-Business Suite instance.
   2. Source the application tier environment file.
   3. Start AdminServer with the following command:

      $ $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

8. Start the Managed Servers. For the first time, all Managed Servers should be started from the WebLogic Server Admin console. This step will create boot.properties files for the respective Managed Servers. Follow these steps:
   1. Log in to the WebLogic Server Administration Console.
   2. Start all Managed Servers, one at a time.
9. Shut down all the Managed Servers. This is so the new credentials will be picked up at the next startup. Follow these steps:
   1. Log in to the WebLogic AdminServer console.
   2. Shut down all Managed Servers.
   3. Shut down AdminServer.
10. Shut down Node Manager using the normal AD script.

    $ $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

11. Copy the boot.properties file for each Managed Server.
    WebLogic Server native scripts use the boot.properties file. The above steps have created the boot.properties file under <EBS_DOMAIN_HOME>/servers/<Managed Server name>/data/nodemanager, which is used by Node Manager. For each Managed Server, copy the newly-generated boot.properties file from<EBS_DOMAIN_HOME>/servers/<Managed Server name>/data/nodemanager to <EBS_DOMAIN_HOME>/servers/<Managed Server name>/security.
    The EBS WebLogic Server domain password has now been changed, and all servers can now be started using the normal AD scripts.
    To start AdminServer:

    $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

    To start the Managed Servers:

    $ $ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start <managed_server_name>

12. The above steps have changed the Oracle WebLogic AdminServer password on the run file system. You now need to perform an fs_clone operation, to change the WebLogic EBS Domain password on the patch file system:
    1. Launch a new session and connect to the Oracle E-Business Suite instance.
    2. Source the application tier environment file.
    3. Run the following command:

       $ adop phase=fs_clone

Adding connection filter in EBS

cd $ADMIN_SCRIPTS_HOME

sh adadminsrvctl.sh start

-- add all nodes from run fs

--------------------------

. ~/EBSapps.env run

java -cp $CLASSPATH:$FMW_HOME/wlserver_10.3/server/lib/weblogic.jar oracle.apps.ad.tools.configuration.RegisterNodePreReq add-filter-rule \

-contextfile $CONTEXT_FILE -hostname <isupplier node hostname>

--------------------------

perl adpreclone.pl appsTier -- ## 25 minutes -- started 3.31pm

Convert Number of Minutes to Hours and Minutes in Microsoft Excel

Excel stores Date and Time in number form. To convert hours from one standard time format to others, we can use the CONVERT Function.

CONVERT function converts a number from one measurement system to another.
Syntax:

=CONVERT(number,from_unit,to_unit)

Let’s do this with an example

In column A, we have Minutes &we need to convert the number of Minutes to Hours in column B.

The second argument in the Convert Function is from_unit which is “mn” for Minutes.

In the third argument enter or select to_unit as “hr” for Hour.

Applying the above formula

=CONVERT(A2,"mn","hr")

Copy the formula in other cells, select the cells taking the first cell where the formula is already applied, use shortcut key CTRL + D.

Desired output will be like shown below

Hope you learned how to use conversion using CONVERT function. You can perform these functions Excel 2013 and 2010. Explore more articles on conversion here. Please let us know if you have any unresolved query. We will help you.

Related Articles:

Connecting to Teradata Database With LDAP Using Oracle SQL Developer

In this article, I will describe how to connect to the Teradata database via LDAP. We will do this with Oracle SQL Developer.

With Oracle SQL Developer, it is possible to connect to many databases with JDBC driver, not just an Oracle database. Some of these are DB2, Teradata, Access, MSSQL, and MySQL. In this article, I will describe how to connect to a Teradata database configured with LDAP Authentication.

I want to connect to Teradata database version 15. The version of Oracle SQL Developer is 4.1.5.

First, I need a Teradata JDBC driver to connect to Teradata from Oracle SQL Developer. You can download this driver by following the link.

After downloading the ZIP/TAR file containing the driver, we need to extract it to the appropriate location on our computer. Then, we need to show the files tdgssconfig.jar and terajdbc4.jar, which will come out of this file in Oracle SQL Developer.

We extract the files from Oracle SQL Developer by clicking on the Add Entry button in the window accessed by following the corresponding path (Tools > Preferences > Database > Third-Party JDBC Drivers). Then click the OK button to close the screen.

Now that we have the relevant drivers displayed, let's open the new connection setup screen through Oracle SQL Developer.

When we open the connection screen, we see that the Teradata connection tab comes right next to the Oracle option — proof that your JAR files are correctly defined. Now, we have the last step we need to make to connect. In the last step, we will add the LOGMECH parameter to our connection to determine how to provide our connection via LDAP. Since we do not have this option on the connection screen by default, we will click the Add button to add this parameter, and when we press the OK button after selecting LOGMECH parameter in the popup window, we will see that this parameter is added as a selection button on the connection setup screen. Then, we will select LDAP with this selection button and we will complete the process.

 

Now we can connect to the Teradata database using our LDAP information and database connection string.

Open Source Softwares

https://sourceforge.net/directory/business-enterprise/project-management/os:windows/

Using SQL Developer to connect to SQL Server databases

http://www.snapdba.com/2013/10/using-sql-developer-to-connect-to-sql-server-databases/#.XdOYYFczaM8

Apparently, being able to use Oracle’s SQL Developer to connect to SQL Server databases has been around for a while (via third party drivers), but I only started using it today for the first time, with SQL Developer 4 EA2 after my colleague mentioned it to me this afternoon 

First of all, thanks to DJ’s blog here as a base for the instructions that follow.  Here’s how you can set this up:

1. Download the jTDS 3rd party JDBC driver, version 1.2.8 from here (I’ve not personally tested with other versions).
2. Save and extract the contents of the jtds-1.2.8-dist.zip file somewhere safe (I extracted mine under “C:\oracle\sqldeveloper\add-ons\jtds-1.2.8-dist\”).
3. Start SQL Developer go to Tools > Preferences > Database > Third Party JDBC Drivers.
4. Click “Add Entry”, point to the ‘jtds-1.2.8.jar’ file location, then select it and click OK.
5. Create a new connection, and choose the “SQLServer” tab.
6. Enter the following details: Connection Name (required for database retrieval), Username, Password, Hostname, and Port.
7. Click “Retrieve database” and select the appropriate database, then Save/Test/Connect as you would do normally.

You’ll notice from the screen shot above that you can also use this to connect to Sybase databases, although I’ve not tried this out myself.

UPDATE: If you at any point decide to use Windows authentication to connect (like I just did), then you might hit this error:

Status : Failure -I/O Error: SSO Failed: Native SSPI library not loaded. Check the java.library.path system property.

…I quickly found a work around, which involved copying the “..\jtds-1.2\x64\SSO\ntlmauth.dll” file from the jTDS directory to the “%JAVA_HOME%\jre\bin” folder.  Then I restarted SQL Developer and it all worked fine