Pages

Sunday, May 29, 2011

Bash Script To Remove Files Older Than 7 Days

find /path -name "*" -mtime +7 -exec rm -f {} \ ;

How to control access to the database and understand validnode checking

You can configure the sqlnet.ora file to allow and deny access to the database
via the validnode checking parmeters.


TCP.VALIDNODE_CHECKING
Use to specify whether to screen access to the database.Value is either YES or ON

TCP.EXCLUDED_NODES
Use to specify which clients using the TCP/IP protocol are denied access to the database.
Hostname and ipaddress can be used

TCP.INVITED_NODES
Use to specify which clients using the TCP/IP protocol are allowed access to the database.
Hostname and ipadddress can be used.


Example sqlnet.ora file (set where database is running)

TCP.VALIDNODE_CHECKING = YES
TCP.EXCLUDED_NODES= (138.3.33.33)
TCP.INVITED_NODES=(138.4.44.44, hammer)

Hide Diagnostics Menu Entry In Oracle Applications

Use the system profiles: 'Hide Diagnostics menu entry'
to control the visibility of the Diagnostics menu

Sunday, May 1, 2011

Invalid Objects

select owner, object_name, object_type

from all_objects

where status != 'VALID'

order by owner, object_type, object_name;

How to find an AD patchset level

select PATCH_LEVEL from fnd_product_installations where APPLICATION_ID=50;

Configuring VNC

Created by: eng.Abd el Rahman Samy

Log in as root then:

•Set your VNC password by the command:
vncpasswd

•Edit /etc/sysconfig/vncservers so that it contains the line:
VNCSERVERS="1:root"

•Enable vncserver as a system service.
chkconfig --level 345 vncserver on

•Start vncserver so it creates the user's xstartup file.
service vncserver start

•Stop vncserver.
service vncserver stop

•Edit /root/.vnc/xstartup and uncomment the first two lines started with ( unset & exec ) to be run.

•Start vncserver.
service vncserver start
Test the connection by running VNC viewer on the windows machine

•Enter server name then session number in the vncviewer as:
:1

Limiting Active Requests by User

As System Administrator you can limit the number of requests that may be active (status of Running)
for an individual user. This ensures that a user cannot monopolize the request queue. For example,
if a user with an Active Request Limit of 5 submits 20 requests, only 5 requests will be run at the same time.
The remaining requests will be run when the number of active requests for the user drops below 5.
Use the Profile Options window to set the Concurrent: Active Request Limit profile.
To set a global limit for all users, set this option at the site level.
You can then modify limits for individual users by setting this profile option at the User level.