Introduction:
after setting up the ssh private and public key, error message coming "Server refused our key"
Resolution:
Check the following steps and check if it resolve the issue.
1- login to server and switch to root user
2- go to /home/user_not_connecting_with_ssh e.g. /home/testuser
3- go to .ssh
4- vi the authorized_keys
5- insert the following on the first line and make sure there is space at the end of the following
ssh-rsa
6- test the issue
Steps to rest the EBS Cloud Manager password when current password not working
1. Make sure no jobs are running in EBS Cloud Manager UI.
2. Make sure NodeJS, Quartz server, Chef server and MySQL Database server are down.
$ ps aux | awk '/[s]erver.js/'
$ ps aux | awk '/[j]ob_scheduler.sh/'
$ ps aux | awk '/[m]ysqld/'
$ ps aux | awk '/[o]c_erchef/'
2.1 If they are running, bring them down:
A. for NodeJS: $ sudo pkill -f server.js
B. for Quartz server: $ sudo pkill -f job_scheduler.sh
: $ sudo pkill -f quartz-2.2.3.jar
C. for Chef server: $sudo chef-server-ctl stop
D. MySQL Database server: $ sudo pkill -f mysqld
3. Create file /tmp/resetpassword.ini with 777 permission
$ touch /tmp/resetpassword.ini
$ chmod 777 /tmp/resetpassword.ini
4. Using ViM Add below content to file : /tmp/resetpassword.ini
ALTER USER 'root'@'localhost' IDENTIFIED BY 'Reset@123';
ALTER USER 'ebsoc'@'localhost' IDENTIFIED BY 'Reset@123';
ALTER USER 'quartz'@'localhost' IDENTIFIED BY 'Reset@123';
FLUSH PRIVILEGES;
5. Stat mysql server
$ sudo mysqld --init-file=/tmp/resetpassword.ini --user=mysql &
6. Kill the process
$ sudo pkill -f mysqld
7. Remove file /tmp/resetpassword.ini
$ rm -f /tmp/resetpassword.ini
8. Restart all services and when prompted, enter the new Cloud Manager admin password
$ cd /u01/install/APPS/apps-unlimited-ebs/bin
$ sh ebscloudmgrctl.sh startall
Introduction:
-ERROR: Invalid Oracle E-Business Suite Cloud Manager Administration Password -
-Reset EBS Cloud manager password when current password not working
Resolution:
Following command can be used to reset password if the current password is working
./ebscmadmin change-admin-password
But if the current password is not working then follow the following steps to reset the EBC Cloud manager administrator password.
Steps:
1. Make sure no jobs are running in EBS Cloud Manager UI.
2. Make sure NodeJS, Quartz server, Chef server and MySQL Database server are down.
$ ps aux | awk '/[s]erver.js/'
$ ps aux | awk '/[j]ob_scheduler.sh/'
$ ps aux | awk '/[m]ysqld/'
$ ps aux | awk '/[o]c_erchef/'
2.1 If they are running, bring them down:
A. for NodeJS: $ sudo pkill -f server.js
B. for Quartz server: $ sudo pkill -f job_scheduler.sh
: $ sudo pkill -f quartz-2.2.3.jar
C. for Chef server: $sudo chef-server-ctl stop
D. MySQL Database server: $ sudo pkill -f mysqld
3. Create file /tmp/resetpassword.ini with 777 permission
$ touch /tmp/resetpassword.ini
$ chmod 777 /tmp/resetpassword.ini
4. Using ViM Add below content to file : /tmp/resetpassword.ini
ALTER USER 'root'@'localhost' IDENTIFIED BY 'Reset@123';
ALTER USER 'ebsoc'@'localhost' IDENTIFIED BY 'Reset@123';
ALTER USER 'quartz'@'localhost' IDENTIFIED BY 'Reset@123';
FLUSH PRIVILEGES;
5. Stat mysql server
$ sudo mysqld --init-file=/tmp/resetpassword.ini --user=mysql &
6. Kill the process
$ sudo pkill -f mysqld
7. Remove file /tmp/resetpassword.ini
$ rm -f /tmp/resetpassword.ini
8. Restart all services and when prompted, enter the new Cloud Manager admin password
$ cd /u01/install/APPS/apps-unlimited-ebs/bin
$ sh ebscloudmgrctl.sh startall
Introduction:
OCI EBS Cloud Manager giving errors of "User profile validation failed".
and it was giving the following messages to resolve the error, but it did not work.
User Profile Validation failed - Make sure following is done
1. Provide the correct "OCI userID"
2. Upload the corresponding public key to OCI console (IAM). If the public key has already been uploaded to OCI, please wait for few minutes before retry the validation.
Resolution:
Checked the user ebs_cloud_manager details with the navigation "Identity & Security > Identity > Domains > Default domain > Users " and found the group "Application Administrator" was missing.
Added the group with the following navigation on OCI Console, and it resolved the errors.
Identity & Security > Identity > Domains > Default domain > Security > Administrators > Application Administrator
Oracle 19c - patch 19.22 unavailability for Windows platform
Having upgraded the Oracle 11g 11.2.0.4 database to Oracle 19c 19.3.0.0.0 while applying the latest patch 19.22 discovered that 19.22 patch is still not released for the Windows platform, raised a SR with Oracle support and they confirmed that 19.22 patch for Windows platform is yet to be released, and they have requested the internal development team to release the 19.22 patch for Windows platform, hope it helps for the shops which are trying to do the latest set of patches 19.22 for their databases on Windows platform.
Oracle 11g 11.2.0.4 upgrade to Oracle 19c 19.3.0.0.0 failing with error ORA-01034
Solution:
glogin.sql file is causing something that upgrade would fail with error ORA-01034, the simple solution is to rename the glogin.sql file and re-run the upgrade process and it will catch up from the point it failed, hope it helps.
Oracle Weblogic 12.2.1.3.0
60820: Select a domain which is a compatible with this environment.
stopComponent.sh and startComponent.sh gives the following errors
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Reading domain from /<PATH>/user_projects/domains/IDMDomain
Error: runCmd() failed. Do dumpStack() to see details.
Error: Error reading domain:
60820: Unsupported Domain
60820: This domain is a managed domain. It has been scaled out from the original domain.
60820: Select a domain which is a compatible with this environment.
Exiting WebLogic Scripting Tool.
This condition is a result of Bug 25964279 (internal / not published in MOS). Due to Bug 25964279, the startComponent.sh and stopComponent.sh scripts can only successfully complete from the first node in an OID 12c collocated cluster.
Execute the startComponent.sh and stopComponent.sh scripts only from the first server node in the collocated cluster.
Alternately an OID instance may be started from a WLST session with one of the following commands :
WLST connected to the target NodeManager:
nmStart(serverName='<COMPONENT_NAME>',serverType='OID')
Replace '<COMPONENT_NAME>' with the OID component name, e.g. 'oid1' or 'oid2'
Introduction: after setting up the ssh private and public key, error message coming "Server refused our key" Resolution: Check th...
