The rhq-server.sh script can be managed by the init process so that the server starts automatically when the system boots. This also allows the server process to be managed by services like service and chkconfig
Environment :
Red Hat JBoss Operations Network (ON) 3.3
Step 1 :
Copy the rhq-server.sh script into the /etc/init.d/ directory.
cp serverRoot/bin/rhq-server.sh /etc/init.d/
Step 2 :
Edit the /etc/init.d/rhq-server.sh script to set the RHQ_SERVER_HOME variable to the JBoss ON server install directory and the RHQ_SERVER_JAVA_HOME variable to the appropriate directory for the JVM.
For example:
RHQ_SERVER_HOME=serverRoot/jon-server-3.3.0.GA
RHQ_SERVER_JAVA_HOME=/usr/
Step 3 :
Edit the /etc/init.d/rhq-server.sh script, and add the following lines to the top of the file, directly under #!/bin/sh
#!/bin/sh
#chkconfig: 2345 95 20
#description: JBoss Operations Network Server
#processname: run.sh
The last two numbers in the #chkconfig: 2345 95 20 line specify the start and stop priority, respectively, for the JBoss ON server
Step 4 :
Add the service to the chkconfig service management command, and verify that it was added properly
chkconfig –add rhq-server.sh
chkconfig rhq-server.sh –list
Step 5 :
Set the rhq-server.sh service to run at run level 5
chkconfig –level 5 rhq-server.sh on
Posted by Unknown at 9:24 PM 1 comment: Links to this post
RMAN-05541: no archived logs found in target database
SYMPTOMS :
Getting RMAN-05541 error when duplicating database from a consistent (cold) RMAN backup
Error Message:
RMAN-00571: ============================================
RMAN-00569: ========== ERROR MESSAGE STACK FOLLOWS ==========
RMAN-00571: ============================================
RMAN-03002: failure of Duplicate Db command at 07/08/2014 18:12:40
RMAN-05501: aborting duplication of target database
RMAN-05541: no archived logs found in target database
SOLUTION :
The error should be resolved by using NOREDO clause in the duplicate command.
run
{
set until time “to_date(’08-OCT-2014 10:15:00′,’DD-MON-YYYY HH24:MI:SS’)”;
DUPLICATE DATABASE TO target DB BACKUP LOCATION ‘/backup_Location’ NOREDO;
}
Posted by Unknown at 8:18 PM No comments: Links to this post
INSTALLING ADDITIONAL JBOSS AGENT PLUG-INS
Environment :
Red Hat JBoss Operations Network (ON) 3.3
Step 1 :
Download the plug-in JAR files from the Customer Support Portal.
In the Customer Support Portal, click Software, and then select the JBoss ON for Plug-in drop-down box.
Step 2 :
Download the plug-in packs.
Step 3 :
Unzip the additional plug-in packs. This creates a subdirectory with the name jon-plugin-pack-plugin_name-3.3.0.GA1.
Step 4 :
List the current contents of the JBoss ON server plug-in directory.
For example:
[root@server rhq-agent]# ls -l serverRoot/jon-server-3.3.0.GA1/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins
Step 5 :
Stop the JBoss ON server.
serverRoot/jon-server-3.3.0.GA1/bin/rhqctl stop
Step 6 :
Copy the new plug-ins from the jon-plugin-pack-plugin_name-3.0.0.GA1/ directory to the JBoss ON server plug-in directory.
[root@server rhq-agent]# cp /opt/jon/jon-server-3.0.0.GA1/jon-plugin-pack-plugin_name-3.0.0.GA1/* serverRoot/jon-server-3.0.0.GA1/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins
Step 7 :
Start the JBoss ON server again.
serverRoot/jon-server-3.0.0.GA1/bin/rhqctl start
Step 8 :
Have the agents reload their plug-ins to load the new plug-ins. This can be done from the command line using the agent’s plugins command:
> plugins update
This can also be done in the JBoss ON GUI by scheduling an update plugins operation for an agent or a group or agents.
Posted by Unknown at 5:16 PM No comments: Links to this post
ORA-15260 While Creating an ASM Diskgroup in 11gR2
APPLIES TO :
Oracle Database – Enterprise Edition – Version 11.2.0.1 to 11.2.0.4 [Release 11.2]
SYMPTOMS :
Running an ASM command and getting ORA-15260
SQL> conn / as sysdba
Connected.
SQL> create diskgroup dg5 external redundancy disk ‘/dev/sda10′,’/dev/sda11’;
create diskgroup dg5 external redundancy disk ‘/dev/sda10′,’/dev/sda11’
*
ERROR at line 1:
ORA-15260: permission denied on ASM disk group
SQL> alter diskgroup data rebalance power 11;
alter diskgroup data rebalance power 11
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15260: permission denied on ASM disk group
CAUSE :
We have logged in with SYSDBA privilege, that is not allowed for ASM operations
SOLUTION :
Login with SYSASM credentials for ASM operations
SQL> conn / as sysasm
Connected.
SQL> create diskgroup dg5 external redundancy disk ‘/dev/sda10′,’/dev/sda11’;
Diskgroup created.
Posted by Unknown at 5:05 PM No comments: Links to this post
How do I configure the SMTP settings in JBoss ON so it can send email alert notifications?
Environment :
Red Hat JBoss Operations Network (ON)
2.3
2.4
3.1
3.2
3.3
Issue :
Not able to send mail through JON server.
Solution :
The SMTP properties are configured in $JON_SERVER/bin/rhq-server.properties with the rhq.server.email.* properties:
By default the rhq-server.properties file has the below parameters and we need to change as per our environment
# Email settings used to connect to an SMTP server to send alert emails.
rhq.server.email.smtp-host=<SMTP Server Address>
rhq.server.email.smtp-port=<SMTP Server Port#> <– Default Port# 25
rhq.server.email.from-address=rhqadmin@localhost
After configuring the properties the JBoss ON Server must be restarted.
For JBoss ON versions prior to 3.2, the following document: How can I confirm my server’s email/SMTP settings are correct? describes how to test the email settings.
For JBoss ON 3.2 and 3.3 confirm server’s email/SMTP settings are correct use below link:
http://<JON-IP/hostname>:7080/coregui/#Test/ServerAccess/EmailTest
Note: 550 is the SMTP reply code for “mailbox unavailable”.
Diagnostic Steps
If it still does not work, enable DEBUG to org.jboss.as.mail for more verbose logging.
Posted by Unknown at 4:53 PM No comments: Links to this post
Wednesday, May 2, 2018
ORA-27300, ORA-27301, ORA-27302,ORA-27303:
$ sqlplus / as sysdba
SQL*Plus: Release 12.1.0.2.0 Production on Wed Apr 30 12:35:25 2018
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected.
SQL> startup;
ORA-27300: OS system dependent operation:invalid_egid failed with status: 1
ORA-27301: OS failure message: Operation not permitted
ORA-27302: failure occurred at: skgpwinit6
ORA-27303: additional information: startup egid = 1000 (oinstall), current egid = 1001 (dba)
SQL> shut immediate;
ORA-27300: OS system dependent operation:invalid_egid failed with status: 1
ORA-27301: OS failure message: Operation not permitted
ORA-27302: failure occurred at: skgpwinit6
ORA-27303: additional information: startup egid = 1000 (oinstall), current egid = 1001 (dba)
Alert Log file last content below:-
At alert log ORA-27140: attach to post/wait facility failed
ORA-27300: OS system dependent operation:invalid_egid failed with status: 1
ORA-27301: OS failure message: Operation not permitted
ORA-27302: failure occurred at: skgpwinit6
ORA-27303: additional information: startup egid = 1000 (oinstall), current egid = 1001 (dba)
2018-04-30T12:40:21.796988-04:00
Process J000 died, see its trace file
2018-04-30T12:40:21.797204-04:00
kkjcre1p: unable to spawn jobq slave process
2018-04-30T12:40:21.797384-04:00
Solution:-
Before we go on and involve clusterware, let’s replay the scenario (changing the group of the oracle executable) manually outside of clusterware to see if we can get the same behaviour
Solution for this problem is quite simple, go view this file
-rwxr-x–x 1 oracle asmadmin 232473728 Apr 30 12:59 /u01/app/oracle/product/12.1.0.2/db_1/bin/oracle
Change file group ownership back to oinstall and restart the database/ASM instance.
-rwxr-x–x 1 oracle oinstall 232473728 Apr 30 12:59 /u01/app/oracle/product/12.1.0.2/db_1/bin/oracle
Posted by anil
