unix file permission number, what each number means

. 1 = execute only. 
2 = write only. 
3 = write and execute (1+2) 
4 = read only.
 5 = read and execute (4+1) 
6 = read and write (4+2) 
7 = read and write and execute (4+2+1)

ForgeRock OpenAM exporting and importing servers configuration using ssoadm command

In order to export server configuration from ForgeRock OpenAM server run the following command that is under

../../openamtools/admin/.../bin


./ssoadm export-svc-cfg -u [adminID] -f [passwordfile] -e [secretkey] -o [outputfile]

Where

-u is username that have full admin rights to export the configuration

-f is password file

-e secretkey  is the secure key that you want to use to encrypt the file. you have to use same key when you import the configuration. you can use any keyword "abcd"

-o this the name of xml file that will contain all the configuration information.



To Import the configuration;

use below command

./ssoadm import-svc-cfg -u [adminID] -f [passwordfile] -e [secretkey] -X [XMLfile]

ForgeRock OpenDJ installation steps

 ForgeRock OpenDJ installation is same as we install ODSEE or any other DS instance. to Install the OpenDJ Toolkit Perform the following in the Root window as the root user

 1. The OpenDJ Toolkit has been downloaded from http://forgerock.org.
Navigate to the /OpenDJ folder and copy the downloaded file.
# cp /opt/fr-462/software/opendj-ldap-toolkit2.6.0.zip /OpenDJ
# cd /OpenDJ

 2. Extract the files in the ZIP file.  For instance, if you downloaded the 2.6- version of the OpenDJ Toolkit you would enter the following:
# unzip opendj-ldap-toolkit-2.6.0.zip This will create a new folder containing the extracted files (for instance, opendj-ldap-toolkit-2.6.0).

 3.  Rename the new folder to opendjtk. # mv opendj-ldap-toolkit-2.6.0 opendjtk 


 4. Add the /OpenDJ/opendjtk/bin folder to your PATH variable.

 5. Verify that you can locate the tool kit tools. # which searchrate 

Oracle 12C database abnormal shutdown solution

If Anytime Oracle Database goes down abnormally, due to machine failure or server reboot, most of the times objects gets into "INVALID" state.


command to check the status
select object_name,status from dba_objects where status='INVALID';

if you see a lot of INVALID objects run the following command after login to SQL

../../dbhome/rdbms/admin

run following utility to recompile these objects

SQL>@utlrp.sql

OAM command to dump all url from OAM server

This command should dump the URIs from the existing OAM server. Just change the path and the application domain.


OAM_REG_HOME=<MW_HOME>middleware/Oracle_IDM1/oam/server/rreg

./bin/oamreg.sh agentValidate <application_domain>

OAAM 11gr1ps2 enabling logging and exporting configuration

Enable trace in OAAM Server
- Log in to Fusion Middleware Control console (hostname:7001/em)
- On the left pane go to Farm_IAMDomain -> WebLogic Domain -> IAMDomain -> oaam_server_server1 (you might have different domain name or server names).
- From the top of the right pane, under oaam_server_server1, select WebLogic server -> Logs -> Log Configuration.
- Go to Log Levels tab, expand the Root logger -> Oracle node and change the level for oracle.oaam to TRACE:32.


Exporting OAAM properties.
To export OAAM properties -> go to oaam_admin console -> Properties -> leave the Search fiels empty -> run Search -> click on Row in the left corner of the properties table to select all -> Actions -> export selecte

OAM export policies error Traceback (innermost last): File "", line 1, in ? NameError: exportPolicy

wls:/oam_domain/serverConfig> exportPolicy(PathTempOAMPolicyFile='/tmp/pre_upgrade_oam.xml')

Traceback (innermost last):

  File "<console>", line 1, in ?

NameError: exportPolicy

wls:/oam_domain/serverConfig> exportPolicy('/tmp/policy_export.xml')

Traceback (innermost last):

  File "<console>", line 1, in ?

NameError: exportPolicy

wls:/oam_domain/serverConfig> exit()

Solution:

you are running wlst.sh command from wrong place. it should be run from $ORACLE_HOME/common/bin/wlst.sh

find where is ORACLE_HOME/common/bin

and run 

wlst.sh

wls:/oam_domain/serverConfig> exportPolicy('/tmp/policy_export.xml')

Successfully exported policies. Check log file for details.

if you got below error use  command without path

wls:/oam_domain/serverConfig> exportPolicy(PathTempOAMPolicyFile='/tmp/pre_upgrade_oam.xml')

Traceback (innermost last):

  File "<console>", line 1, in ?

TypeError: exportPolicy() got an unexpected keyword argument 'PathTempOAMPolicyFile'

use command without PathTempOAMPolicyFile

wls:/oam_domain/serverConfig> exportPolicy('/tmp/policy_export.xml')