Linux

To enable the Xmanager the packages required to install are

xorg-x11-xauth-1.0.2-7.1.el6.x86_64.rpm

xterm-253-1.el6.x86_64.rpm

xorg*

Quote:
yum groupinstall "X Window System" "GNOME Desktop Environment"

need KDE

yum groupinstall "X Window System" KDE

need XFCE
yum groupinstall "X Window System" XFCE

yum -y groupinstall "X Window System" "Desktop" "Fonts" "General Purpose Desktop"

On Linux server

http://www.elinuxbook.com/tigervnc-server-configuration-remote-desktop-application-for-linux/

https://www.linuxtechi.com/install-configure-vnc-server-centos-7-rhel-7/

Download from http://tigervnc.org/

Copy tigervnc-1.8.0.x86_64.tar.gz

install Desktop Environment and X Windows System packages.

yum -y groupinstall "Desktop" "GNOME Desktop Environment" "X Window System"

To test the website is reachable:

time curl -I http://yourpage.com | grep HTTP

Check whether the port is open or not.

netstat -an | grep PORTNUMBER | grep -i listen
netstat -tuplen

telnet hostname port

telnet myserver.com 80

Option #1: lsof command

The syntax is:

$ sudo lsof -i -P -n
$ sudo lsof -i -P -n | grep LISTEN
$ doas lsof -i -P -n | grep LISTEN ### [OpenBSD] ###

Glassfish

0down vote

1- Go to the config folder inside your domain. (In my case: C:\Glassfish\glassfish\domains\mydomain\config\ )

2-Open the file domain

3-Update the port number on these three lines:

4-Restart your domain:

--Note For restarting the domain:

1-Open cmd console

2-Navigate yo your domain

3-Execute: asadmin restart-domain mydomain

--I hope it helps :-)

Tomcat:

1) Locate server.xml in {Tomcat installation folder}\ conf \ 2) Find following similar statement

<Connector port="8080" maxHttpHeaderSize="8192"

maxThreads="150" minSpareThreads="25" maxSpareThreads="75"

enableLookups="false" redirectPort="8443" acceptCount="100"

connectionTimeout="20000" disableUploadTimeout="true" />

For example

<Connector port="8181" protocol="HTTP/1.1"

connectionTimeout="20000"

redirectPort="8443" />

Edit and save the server.xml file. Restart Tomcat. Done

In order to access /manager/html url, you need to do below change in context.xml of manager app. 1. Go to /apache-tomcat-8.5.23/webapps/manager/META-INF location, then edit context.xml

<Valve className="org.apache.catalina.valves.RemoteAddrValve"

allow="^.*$" />

......

</Context>

2. Restart the server.

The case is same for the host manager.

You are not authorized to view this page.

By default the Manager is only accessible from a browser running on the same machine as Tomcat. If you wish to modify this restriction, you'll need to edit the Manager's context.xml file.

If you have already configured the Manager application to allow access and you have used your browsers back button, used a saved book-mark or similar then you may have triggered the cross-site request forgery (CSRF) protection that has been enabled for the HTML interface of the Manager application. You will need to reset this protection by returning to the main Manager page. Once you return to this page, you will be able to continue using the Manager application's HTML interface normally. If you continue to see this access denied message, check that you have the necessary permissions to access this application.

If you have not changed any configuration files, please examine the file conf/tomcat-users.xml in your installation. That file must contain the credentials to let you use this webapp.

For example, to add the manager-gui role to a user named tomcat with a password of s3cret, add the following to the config file listed above.

Note that for Tomcat 7 onwards, the roles required to use the manager application were changed from the single manager role to the following four roles. You will need to assign the role(s) required for the functionality you wish to access.

manager-gui - allows access to the HTML GUI and the status pages
manager-script - allows access to the text interface and the status pages
manager-jmx - allows access to the JMX proxy and the status pages
manager-status - allows access to the status pages only

The HTML interface is protected against CSRF but the text and JMX interfaces are not. To maintain the CSRF protection:

Users with the manager-gui role should not be granted either the manager-script or manager-jmx roles.
If the text or jmx interfaces are accessed through a browser (e.g. for testing since these interfaces are intended for tools not humans) then the browser must be closed afterwards to terminate the session.

For more information - please see the Manager App HOW-TO.

Solution:

<tomcat-user>

</tomcat-users>

YUM REPOSITORY BEGIN
#######################################################################

Use the DVD directly as a Yum repository.
Create a new Yum repository by copying the packages off the DVD.

To use the DVD directly, create a file called "/etc/yum.repos.d/dvd.repo" with the following contents, where the "baseurl" points to your DVD mount point.

[dvd]
name=Oracle Linux Installation DVD
baseurl=file:///media/cdrom
enabled=0

Import the GPG key from the DVD.

# rpm --import /media/cdrom/RPM-GPG-KEY

You can now use the DVD as a Yum repository by referencing it using the "--enablerepo" option.

# yum install --enablerepo=dvd system-config-lvm

If you want to take the second option and create a new Yum repository by copying the packages off the DVD, create a local directory to hold the yum repository and copy the packages to it.

# mkdir /repo
# cp /media/cdrom/Packages/* /repo

To create a repository, we need to install the createrepo package, which requires a couple of dependencies.

# cd /repo
# rpm -ivh deltarpm* python-deltarpm*
# rpm -ivh createrepo*

Now we can create a repository out of the contents of the directory.

# cd /repo
# createrepo .

To allow the yum command to use the repository, we must create a ".repo" file in the "/etc/yum.repos.d" directory. Create a file called "/etc/yum.repos.d/localrepo.repo" with the following contents.

[localrepo]
name=localrepo
baseurl=file:///repo/
enabled=1
gpgcheck=0

Notice the "baseurl" parameter. This indicates the location of the repository. In this case I am using a local file system, so the parameter is set to "file://" followed by the path to the repository "/repo/". If this were an internet repository we would expect a baseurl with a HTTP address. For example, the Oracle Linux repository setting would be as follows.

baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/2/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6

When using internet repositories, you typically expect the "gpgkey" entry as a security precaution.

You should now be able to use the yum command to install packages.

yum

The yum command allows you to install, update, list and remove packages.

# yum install system-config-lvm
# yum update system-config-lvm
# yum list system-config-lvm
# yum remove system-config-lvm

The advantage of yum over the rpm command is it deals with all dependencies for you, prompting you with the required dependencies and the total size of the operation. If you agree, all necessary dependencies will be installed, in addition to your specified package(s).

The main Linux distribution repositories also support package groups, allowing you to install, update or remove entire feature sets using a single command. To check if any groups have been defined in the repository, issue the following command.

# yum grouplist

You can install, update or remove entire groups of packages as follows.

# yum groupinstall "Development Libraries"
# yum groupupdate "Development Libraries"
# yum groupremove "Development Libraries"

YUM REPOSITORY END

#################################################################################

dads.conf file while configuring the apex in OHS

#Alias /i/ "/u01/app/oracle/mw/Oracle_WT1/instances/instance1/config/OHS/ohs1/htdocs/apex_images/"

<Location /apex >
Order deny,allow
PlsqlDocumentPath docs
AllowOverride None
PlsqlDocumentProcedure wwv_flow_file_mgr.process_download
PlsqlDatabaseConnectString 10.22.10.8:1521:prod ServiceNameFormat
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
PlsqlAuthenticationMode Basic
SetHandler pls_handler
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDatabaseUsername APEX_PUBLIC_USER
PlsqlDefaultPage apex
PlsqlDatabasePassword Abc#2018
PlsqlRequestValidationFunction wwv_flow_epg_include_modules.authorize
PlsqlPathAlias r
PlsqlPathAliasProcedure wwv_flow.resolve_friendly_url
Allow from all
</Location>

############################################################################

###########################################################################

Error:

$ ./sqlplus

exec(): 0509-036 Cannot load program sqlplus because of the following errors:

rtld: 0712-001 Symbol CreateIoCompletionPort was referenced

from module /u01/app/oracle/product/12.1.0.2/db_1/lib/libttsh12.so(), but a runtime definition

of the symbol was not found.

rtld: 0712-001 Symbol GetMultipleCompletionStatus was referenced

from module /u01/app/oracle/product/12.1.0.2/db_1/lib/libttsh12.so(), but a runtime definition

of the symbol was not found.

rtld: 0712-002 fatal error: exiting.

Solution:

Website:

https://blogs.sap.com/2015/04/10/error-in-oracle-12c-installation-rtld-0712-001-symbol-createiocompletionport-was-referenced/

Error in Oracle 12C installation – rtld: 0712-001 Symbol CreateIoCompletionPort was referenced

Installed Oracle 12C on AIX Server.

When executing “lsnrctl start” or “lsnrctl status” or sqlplus / as sysdba, error occurred

“rtld: 0712-001 Symbol CreateIoCompletionPort was referenced”.

The problem is due to I/O Communication ports either not enabled or not installed .

To check whether IOCP is installed run the following command

# lslpp -l bos.iocp.rte

As shown above, IOCP module was installed and present in AIX

To check whether IOCP is enabled or not , run the following unix command

# lsdev -Cc iocp

It showed “Defined” means not enabled. The output should show “Available” instead of “Defined”.

To change from Defined to Available is done using unix ‘smitty’ command

# smitty iocp

Select Change / Show Characteristics of I/O Completion Ports.

Change configured state at system restart from Defined to Available.

Run the lsdev command to confirm the IOCP status is set to Available:

# lsdev | grep iocp

iocp0 Available I/O Completion Ports

Perform a system restart (means server reboot) to make the changes permanent.

After the Server reboot, check lsnrctl status or lsnrctl start command or sqlplus / as sysdba command as shown in the screenshot below

Before installing Oracle 12C, read the installation guide properly and follow the instructions as mentioned in the pre-requisite check.

###########################################################################

Error:

SQL> clear scr

SQL> Alter system set log_archive_dest_1='location= /archive/BISPNG' scope=both;

Alter system set log_archive_dest_1='location= /archive/BISPNG' scope=both

ERROR at line 1:

ORA-32017: failure in updating SPFILE

ORA-16179: incremental changes to "log_archive_dest_1" not allowed with SPFILE

SQL> clear scr

SQL> Alter system set log_archive_dest_1='location=/archive/BISPNG' scope=both;

System altered.

Solution: The error was caused due due to the space that exit between location= which get solved after removing the error.

Configuring IOCP on AIX

DB2 installation using the db2setup command or db2_install command enables IOCP and sets the status of the IOCP port to Available.

About this task

This topic describes how to configure I/O completion ports (IOCP) for AIX® 5.3 TL9 and AIX 6.1 TL2 . This version of AIX operating system has the IOCP fileset included as part of the base install.

Procedure

1. Enter the lslpp command to check if the IOCP module is installed on your system:

$ lslpp -l bos.iocp.rte

Copy

The output from the lslpp command should be similar to the following :

Fileset                      Level  State      Description

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

        Path: /usr/lib/objrepos

         bos.iocp.rte               5.3.9.0  APPLIED    I/O Completion Ports API

        Path: /etc/objrepos

        bos.iocp.rte              5.3.0.50  COMMITTED  I/O Completion Ports API

Copy

2. Enter the lsdev command to check if the status of the IOCP port is Available:

$ lsdev -Cc iocp

Copy

o The output from the lsdev command should match the following example:

 iocp0 Available  I/O Completion Ports

Copy

o If the IOCP port status is Defined, change the status to Available:

§ Log in to the server as root and issue the following command:

# smitty iocp

Copy

§ Select the Change / Show Characteristics of I/O Completion Ports. Change configured state at system restart from Defined to Available. Enter the lsdev command again and confirm that the status of the IOCP port is changed to Available.

3.9 Enabling I/O Completion Ports

To ensure successful database, client, and grid infrastructure installation, set IOCP to Available using this procedure.

On IBM AIX on POWER Systems (64-Bit), enable I/O completion ports (IOCP) to ensure successful database and grid infrastructure installation.

To check if the IOCP module is enabled, run the lsdev command:

$ lsdev | grep iocp

The following sample output shows the IOCP status is set to Defined and hence not enabled:

iocp0 Defined I/O Completion Ports

By default, IOCP is set to Defined. To enable IOCP, set IOCP to Available using the following procedure:

# smitty iocp

Select Change / Show Characteristics of I/O Completion Ports.
Change configured state at system restart from Defined to Available.
Run the lsdev command to confirm the IOCP status is set to Available:

5. $ lsdev | grep iocp

iocp0 Available I/O Completion Ports

Restart the system to make the changes permanent.

###############################################################################

https://docs.oracle.com/database/121/UNXAR/strt_stp.htm#UNXAR417

Automatic Shutdown and Startup of the Database:

2 Stopping and Starting Oracle Software

This chapter describes how to identify Oracle Database processes, and provides basic information about how to stop and restart them. It also describes how to set up automatic startup and shutdown of the Oracle Database. It contains the following sections:

· Stopping and Starting Oracle Processes

· Automating Shutdown and Startup

Note:

When using Oracle Restart, you can use Service Control Utility (SRVCTL), a command-line interface, to manage Oracle processes (database instance, listener, Oracle ASM instance). With SRVCTL, you can manage the Oracle Restart configuration, see the status of processes managed by Oracle Restart, and start or stop processes such as Oracle Database. SRVCTL has been enhanced to support single instance databases with Oracle Restart on standalone servers and on clusters with Oracle Clusterware.

See Also:

Oracle Database Administrator's Guide and Oracle Automatic Storage Management Administrator's Guide for more information about SRVCTL commands

2.1 Stopping and Starting Oracle Processes

This section describes how to stop and start Oracle processes. It contains the following topics:

· Stopping and Starting Oracle Database and Oracle Automatic Storage Management Instances

· Stopping and Starting Oracle Restart

2.1.1 Stopping and Starting Oracle Database and Oracle Automatic Storage Management Instances

This section describes how to stop and start Oracle Database and Oracle Automatic Storage Management instances.

2.1.1.1 Stopping an Oracle Database or Oracle Automatic Storage Management Instance

Caution:

Do not stop an Oracle Automatic Storage Management instance until you have stopped all Oracle Database instances that use Oracle Automatic Storage Management instance to manage their storage.

To stop an Oracle Database or Oracle Automatic Storage Management instance:

1. Run the following commands to identify the SID and Oracle home directory for the instance that must be shut down:

On Oracle Solaris:

$ cat /var/opt/oracle/oratab

On other operating systems:

$ cat /etc/oratab

The oratab file contains lines similar to the following, which identify the SID and corresponding Oracle home directory for each database or Oracle Automatic Storage Management instance on the system:

$ORACLE_SID:$ORACLE_HOME:<N|Y>

Note:

Oracle recommends that you use the plus sign (+) as the first character in the SID of Oracle Automatic Storage Management instances.

2. Run the oraenv or coraenv script, depending on the default shell, to set the environment variables for the instance that must be shut down:

o Bourne, Bash, or Korn shell:

o    $ . /usr/local/bin/oraenv

o C shell:

o    % source /usr/local/bin/coraenv

When prompted, specify the SID for the instance.

3. Run the following commands to shut down the instance:

4.  $ sqlplus

5.  SQL> CONNECT SYS as SYSDBA

6.  Enter password: sys_password

7.  SQL> SHUTDOWN NORMAL

After the instance shuts down, you can quit SQL*Plus.

2.1.1.2 Restarting an Oracle Database or Oracle Automatic Storage Management Instance

Caution:

If the database instance uses Oracle Automatic Storage Management for storage management, then you must start the Oracle Automatic Storage Management instance before you start the database instance.

To restart an Oracle Database or Oracle Automatic Storage Management instance:

1. Repeat steps 1 and 2, if required, to set the ORACLE_SID and ORACLE_HOME environment variables to identify the SID and Oracle home directory for the instance you want to start.

2. Run the following commands to start the instance:

3.  $ sqlplus

4.  SQL> CONNECT SYS as SYSDBA

5.  Enter password: sys_password

6.  SQL> STARTUP

After the instance starts, you can exit from SQL*Plus.

2.1.2 Stopping and Starting Oracle Restart

To stop or start Oracle Restart, run the following command:

· Start: This option is used to start Oracle Restart

Syntax and Options:

crsctl start has

· Stop: This option is used to stop Oracle Restart

Syntax and Options:

crsctl stop has

See Also:

Oracle Database Administrator's Guide for more information about the srvctl commands

2.2 Automating Shutdown and Startup

Oracle recommends that you configure the system to automatically start Oracle Database when the system starts, and to automatically shut it down when the system shuts down. Automating database startup and shutdown guards against incorrect database shutdown.

To automate database startup and shutdown, use the dbstart and dbshut scripts, which are located in the $ORACLE_HOME/bin directory. The scripts refer to the same entries in the oratab file, which are applied on the same set of databases. You cannot, for example, have the dbstart script automatically start sid1, sid2, and sid3, and have the dbshut script shut down only sid1. However, you can specify that the dbshut script shuts down a set of databases while the dbstart script is not used at all. To do this, include a dbshut entry in the system shutdown file, but do not include the dbstart entry from the system startup files.

See Also:

The init command in the operating system documentation for more information about system startup and shutdown procedures

2.2.1 Automating Database Startup and Shutdown on Other Operating Systems

To automate database startup and shutdown by using the dbstart and dbshut scripts:

1. Log in as the root user.

2. Edit the oratab file for the platform.

To open the file, use one of the following commands:

o On Oracle Solaris:

o    # vi /var/opt/oracle/oratab

o On IBM AIX on POWER Systems (64-Bit) and Linux:

o    # vi /etc/oratab

Database entries in the oratab file are displayed in the following format:

$ORACLE_SID:$ORACLE_HOME:<N|Y>

In this example, the values Y and N specify whether you want the scripts to start or shut down the database, respectively. For each database for which you want to automate shutdown and startup, first determine the instance identifier (SID) for that database, which is identified by the SID in the first field. Then, change the last field for each to Y.

You can set dbstart to autostart a single-instance database which uses an Automatic Storage Management installation auto-started by Oracle Clusterware. This is the default behavior for an Automatic Storage Management cluster. To do this, you must change the oratab entry of the database and the Automatic Storage Management installation to use a third field with the value Wand N, respectively. These values specify that dbstart auto-starts the database only after the Automatic Storage Management instance is started.

Note:

If you add new database instances to the system and automate the startup for them, then you must edit the entries for those instances in the oratab file.

3. Change directory to one of the following, depending on the operating system:

Platform	Initialization File Directory
Linux and Oracle Solaris	`/etc/init.d`
IBM AIX on POWER Systems (64-Bit)	`/etc`

5. Create a file called dbora, and copy the following lines into this file:

Note:

Change the value of the ORACLE_HOME environment variable to specify the Oracle home directory for the installation. Change the value of the ORACLE environment variable to the user name of the owner of the database installed in the Oracle home directory (typically, oracle).

#! /bin/sh

# description: Oracle auto start-stop script.

# Set ORACLE_HOME to be equivalent to the $ORACLE_HOME

# from which you wish to execute dbstart and dbshut;

# Set ORA_OWNER to the user id of the owner of the

# Oracle database in ORACLE_HOME.

ORA_HOME=<Type your ORACLE_HOME in full path here>

ORA_OWNER=<Type your Oracle account name here>

case "$1" in

'start')

    # Start the Oracle databases:

    # The following command assumes that the oracle login

    # will not prompt the user for any values

    # Remove "&" if you don't want startup as a background process.

    su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart $ORA_HOME" &

    touch /var/lock/subsys/dbora

;;

'stop')

    # Stop the Oracle databases:

    # The following command assumes that the oracle login

    # will not prompt the user for any values

    su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut $ORA_HOME" &

    rm -f /var/lock/subsys/dbora

;;

esac

Note:

This script can only stop Oracle Net listener for which a password has not been set. In addition, if the listener name is not the default name, LISTENER, then you must specify the listener name in the stop and start commands:

$ORACLE_HOME/bin/lsnrctl {start|stop} listener_name

6. Change the group of the dbora file to the OSDBA group (typically dba), and set the permissions to 750:

7.  # chgrp dba dbora

8.  # chmod 750 dbora

9. Create symbolic links to the dbora script in the appropriate run-level script directories, as follows:

Platform	Symbolic Links Commands
Oracle Solaris	# ln -s /etc/init.d/dbora /etc/rc0.d/K01dbora # ln -s /etc/init.d/dbora /etc/rc3.d/S99dbora
Linux	# ln -s /etc/init.d/dbora /etc/rc.d/rc0.d/K01dbora # ln -s /etc/init.d/dbora /etc/rc.d/rc3.d/S99dbora # ln -s /etc/init.d/dbora /etc/rc.d/rc5.d/S99dbora
IBM AIX on POWER Systems (64-Bit)	# ln -s /etc/dbora /etc/rc.d/rc2.d/S99dbora # ln -s /etc/dbora /etc/rc.d/rc0.d/K01dbora

###############################################################################

countries

Error Solution

Option #1: lsof command

yum

Error in Oracle 12C installation – rtld: 0712-001 Symbol CreateIoCompletionPort was referenced

Configuring IOCP on AIX

2 Stopping and Starting Oracle Software

2.1 Stopping and Starting Oracle Processes

2.1.1 Stopping and Starting Oracle Database and Oracle Automatic Storage Management Instances

2.1.1.1 Stopping an Oracle Database or Oracle Automatic Storage Management Instance

2.1.1.2 Restarting an Oracle Database or Oracle Automatic Storage Management Instance

2.1.2 Stopping and Starting Oracle Restart

2.2 Automating Shutdown and Startup

2.2.1 Automating Database Startup and Shutdown on Other Operating Systems

No comments:

Post a Comment