Oracle jgaicc

avril 28, 2011

Oracle Public Yum Server

Filed under: Uncategorized — jgaicc @ 2:36
  1. Oracle Linux 6
    # cd /etc/yum.repos.d
    # wget
    Oracle VM 2
    # cd /etc/yum.repos.d
    # wget
  2. Enable the appropriate repository by editing the yum configuration file

    • Open the yum configuration file in a text editor
    • Locate the section in the file for the repository you plan to update from, e.g. [el4_u6_base]
    • Change enabled=0 to enabled=1
  3. Begin using yum, for example:

    yum list

    yum install firefox

You may be prompted to confirm the import of the Oracle OSS Group GPG key.

Frequently Asked Questions …

Oracle Public Yum Server

Signer ses propres certificats SSL « EASYTEAM LE BLOG

Filed under: Uncategorized — jgaicc @ 11:51


Signer ses propres certificats SSL « EASYTEAM LE BLOG

Les composants d’une PKI libre 1 . Tous les serveurs et proxy d’une PKI libre peuvent fonctionner avec Linux ou, dans le cas des autorités, avec OpenBSD, plus sécurisé.

2 . La bibliothèque OpenSSL permet la création d’une usine à certificats.

3 . Le serveur web Apache peut fournir les services pour l’interface avec l’autorité de certification par le biais de ModSSL et vers l’annuaire (pour du webSSO) grâce aux modules AuthLDAP.

4 . L’annuaire OpenLDAP stocke les profils et les certificats.

5 . Pour les utilisateurs, le navigateur Mozilla assure une navigation sécurisée (SSL) et la signature des e-mails.

DB: Supprimer les objets d’un schéma « EASYTEAM LE BLOG

Filed under: Uncategorized — jgaicc @ 11:48


Supprimer les objets d’un schéma

2 novembre 2010

par yooo13

Il arrive parfois d’avoir besoin de supprimer tous les objets d’un schéma, mais, par facilité ou pour différentes raisons, sans supprimer l’utilisateur. Par défaut la base de données Oracle ne fournit pas d’ordre SQL simple pour effectuer une telle tache. Je vous propose ainsi le petit script suivant pour exécuter cette opération.
Le code assez simple à exécuter en temps que SYS est le suivant :

voir la source



cursor c_get_objects is

select owner, object_type,'"'||object_name||'"'||decode(object_type,'TABLE' ,' cascade constraints purge',null) obj_name

from dba_objects


and owner in ('MYUSER');

cursor c_get_objects_type is

select owner, object_type, '"'||object_name||'"' obj_name

from dba_objects

where object_type in ('TYPE')

and owner in ('MYUSER') ;


for object_rec in c_get_objects


execute immediate ('drop ' || object_rec.object_type || ' ' || object_rec.owner || '.' ||object_rec.obj_name);

end loop;

for object_rec in c_get_objects_type



execute immediate ('drop '||object_rec.object_type || ' ' || object_rec.owner ||'.' || object_rec.obj_name);


end loop;



Et voila un beau schéma tout neuf.

Il se peut que des segments LOB restent coincés. Il faut alors se connecter avec l’utilisateur et purger la corbeille :

voir la source


purge recyclebin ;

Merci à

Supprimer les objets d’un schéma « EASYTEAM LE BLOG

PSOFT PRCS: ya til encore des process running???

Filed under: Uncategorized — jgaicc @ 10:12


By chris | Published April 29, 2010

Never trust your process monitor.  On occasion, you’ll need/want to bounce your process scheduler* and quick check of process monitor will ensure that you won’t wack any running jobs … but beware, the process monitor page can and will lie to you.  Use the following SQL (current as of PT 8.4X) to query the database to actually see what’s running. 

(* bouncing PRCS to remove file and memory cache is not, always, in my opinion, needed as it was a few years ago; however, it’s undenieable effective at ruling out cache issues).

Quick and dirty SQL to do this:

set echo on feed on time on;
set pagesize 50000;

       8,’Cancelled’,9,’Success’,10,’Not Successful’,11,’Posted’,12,’Unable to post’,13,’Resend’,
      14,’Posting’,15,’Content Generated’,16,’Pending’,runstatus) "RUNSTATUS DESC"
from     psprcsrqst
where RUNSTATUS in (6,7)

avril 27, 2011

How to view list of hidden parameters « Coskan’s Approach to Oracle

Filed under: Uncategorized — jgaicc @ 5:40


Here is the query you can use to view the values of hidden parameter. (use it with sys user with sysdba privilages)

/* hidden parameters */

select a.ksppinm name,
b.ksppstvl value,
b.ksppstdf deflt,
(a.ksppity, 1,
‘boolean’, 2,
‘string’, 3,
‘number’, 4,
‘file’, a.ksppity) type,
a.ksppdesc description
sys.x$ksppi a,
sys.x$ksppcv b
a.indx = b.indx
a.ksppinm like ‘\_%’ escape ‘\’
order by

How to view list of hidden parameters « Coskan’s Approach to Oracle

The PeopleSoft DBA Blog

Filed under: Uncategorized — jgaicc @ 5:00


The priority of the category to which a process belongs takes precedence over the priority of the process. Thus a low priority process in a high priority category will be executed by the Process Scheduler in preference to a high priority process in a low priority category. Naturally if two processes are in the same category, or categories of equal priority, the higher priority process will be scheduled first.

The PeopleSoft DBA Blog

Jim’s PeopleSoft Journal

Filed under: Uncategorized — jgaicc @ 4:56


Thursday, February 10, 2011

JavaScript Meta blog

JavaScript is a critical component of PeopleSoft applications. With the web browser pretty much taking over as the rendering engine for enterprise applications, I see JavaScript as a critical language for computer professionals. Of course, technologies like PeopleTools and ADF contain abstraction layers so application developers do not have to write JavaScript, but, in the end, someone has to write the JavaScript generated by those abstraction layers. And, if something goes wrong, odds are very good you will have to dig through the generated JavaScript to see what went wrong (where, when, why, etc).

Anyway, I think JavaScript is one of the most important modern languages a programmer can learn, and I know I’m not alone in this opinion. Of late, I’ve found some very interesting online resources for people interested in learning JavaScript, so I wrote this post to pass those resources along to PeopleSoft developers.

I will maintain this as a "Meta-blog" post and update it as I find more resources. I will attempt to keep the list short, so you don’t have to sift through thousands of irrelevant tutorials. Restated: this is not a complete list. It is just a short list of tutorials that I think stand above the rest.

Posted by Jim Marion at 12:21 PM 8 comments Links to this post

Labels: JavaScript

Jim’s PeopleSoft Journal

PeopleTools 8.50 uses DBMS_APPLICATION_INFO to Identify Database Sessions

Filed under: Uncategorized — jgaicc @ 4:51



PeopleTools 8.50 uses DBMS_APPLICATION_INFO to Identify Database Sessions

I recently worked on a PeopleTools 8.50 system in production for the first time and was able to make use of the new Oracle specific instrumentation in PeopleTools.
PeopleTools now uses the DBMS_APPLICATION_INFO package to set module and action session attributes.  This data is then copied into the Active Session History (ASH).

  • Within the PIA, the application server sets module and action to the name of the current component and page within the current components
  • For Integration Broker messages they are set to service and queue name.
  • For Application Engine processes the module is set to PSAE and the action is set to the program name.

The first two of these three changes are very welcome, but I think the instrumentation of Application Engine is inadequate. I have a better suggestion which can be implemented with a database trigger.
Enterprise Manager
In Oracle Enterprise Manager, I can see the top SQL statements and group them by Module and Action, so I now can see which components are consuming the most time.  I can also produce an AWR for a specific component or page within a component.

OEM Screenshot of a PeopleTools 8.50 system.

I can query the ASH data to profile which pages consume the most time on the database.

MODULE                 ACTION                   ASH_SECS 
---------------------- ---------------------- ---------- 
RECV_PO                PO_PICK_ORDERS                240 
XXX_REQ_INQUIRY        xyzzy                         170 
XXX_REQ_WRKLST         XXX_REQ_WORKLIST              170 
VCHR_EXPRESS           VCHR_LINE_RECV_WRK            170 
XXX_FIN_WORKLIST       XXX_FIN_WORKLIST              160 
VCHR_EXPRESS           VCHR_EXPRESS1                 160 
PURCHASE_ORDER_EXP     PO_EXPRESS                    140 
XXX_HOME_PAGE          XXX_HOME_PAGE                 140 
RECV_PO                RECV_WPO                      130 
VCHR_EXPRESS           xyzzy                         120 
XXX_PUR_WORKLIST       XXX_PUR_WRKLST                120 
CDM_RPT                CDM_RPT_INDEX                 100 
sum                                                  2820

(Updated 19.11.2010) For some components the action is set to ‘xyzzy’. This seems to be a default value set when the component is opened, but before any of the pages are processed.  Therefore, it refers to activity in the search dialogue, including processing of :

  • look ups to obtain values for search criteria
  • SQL issued during SearchSave PeopleCode to validate the search criteria.
  • the query on the Component Search record

Batch Processes

Now, I want to look at what happens in batch processes. In previous versions of PeopleTools, the module was set to the same value as the program name, and action was left blank. This is not particularly helpful. In 8.50 module is set to PSAE for Application Engine processes, and action is set to the name of the program.

MODULE                       ACTION                      ASH_SECS
---------------------------- ------------------------- ----------
PSNVS.EXE                                                   10220
PSAE                         AP_PSTPYMNT                     3100
PSAE                         AP_MATCH                        2690
sqrw.exe                                                     1770
PSAE                         PO_RECVACCR                     1390
PSQRYSRV.exe                                                  880
PSAE                         FS_STREAMLN                      870
PSPUBDSP.exe                                                  850
PSBRKDSP.exe                                                  740
PSPRCSRV.exe                                                  690
PSSUBDSP.exe                                                  620

This is certainly better than in previous versions. However, its weakness is that if I have multiple concurrent instances of the same process, although I could tell that the ASH data had come from different sessions, I would not be determine which came from which session. This situation could occur, for example, in Global Payroll if ‘streaming’ was configured, where the payroll calculation can be broken into many processes that run concurrently.

In another blog posting, Using Oracle Enterprise Manager (Grid Control) with PeopleSoft, I proposed a trigger that writes name of the PeopleSoft process name to module, and the Process Instance number into action. Furthermore, this trigger works for all processes scheduled by the Process Scheduler.  I think that that trigger is still useful in PeopleTools 8.50.

Posted by David Kurtz at 20:56 3 comments Links to this post

Labels: ASH, DBMS_APPLICATION_INFO, PeopleTools 8.50

Older Posts Home

Subscribe to: Posts (Atom)

The PeopleSoft DBA Blog

People’s Blog for PeopleSoft

Filed under: Uncategorized — jgaicc @ 4:43


Monitoring Application Server September 30, 2010

Posted by neil0605 in PeopleSoft.
Tags: application server, monitoring, PeopleSoft
add a comment

Recently , I came across a situation where an application server domain should be monitored always and whenever it is down , an email should go to concerned team.

Application server was on a windows 2003 server.

To get an email , first of all we need to setup SMTP  in psappsrv.cfg. Then we will require any kind of third party tool like bmail or sendmail. I have used sendmail.

I have written a bat file which runs infinitely , and gather application server status after every 1 minute and take this output in a text file . Whenever application server is up , it will have BBL.exe process running . Search for ‘BBL.exe’ in text file and if found do nothing , delete the text file and continue the infinite loop.

If not found , go to send mail procedure , which will send emails to an individual or a group , and will keep mailing at fixed interval until application server is up.

Enabling Bypass Signon January 24, 2010

Posted by neil0605 in PeopleSoft.
Tags: Forgot Password, People Tools, PeopleSoft, PeopleSoft Signon
add a comment

Happy New year to all of you.Its been long since my last post.

Recently I was implementing forgotten password functionality in PeopleSoft. Earlier it was taken care by Portal. But now customer is decomissioning Portal system they want to implement this functionality on Finance homepage.

The  first step for this was to create a new site and make it bypass signon enabled.

Even for a single server domain , multiple sites can be create. The http port will be same. Once the site is created , make following changes to file and bounce the webserver.

byPassSignOn = True

defaultUserId = <UserId>

defautltPWD = <UserPwd>

Also make public access enabled in Web Profile for the user id given in file.

After that change the PIA link from http://<myserver>/psp/<sitename>/?cmd=login&#160; to  http://<myserver>/psp/<sitename>/?cmd=start.

This change makes webserver to check for bypass signon , and thus didn’t ask for authentication.

Once this is set you can create an userid with appropriate permissions ( which will only access forgotten password component ) and give that as a direct link on the signin.html page.

People’s Blog for PeopleSoft

SchedulerTransfer servlet – posting issue

Filed under: Uncategorized — jgaicc @ 2:30


SchedulerTransfer servlet – posting issue

Issue: Distribution agent failed to post the files to report repository.
Error message: The XML file returned by the web server is invalid. XML document object creation failed.
Solution: This is an issue with SchedulerTransfer servlet which requires authentication. When a report needs to get transfer to report repository, distribution agant use SchedulerTransfer servlet for this purpose. SchedulerTransfer servlet checks for the default local node and if there is no authentication there, it will get fail. The Default Local Node must have the Authentication Option set to ‘Password’. Application server needs a restart post this change.
Navigation below…

Peopletools > Integration Broker > Integration Setup > Nodes > Default Local Node must have Password Authentication

PeopleTools->Portal- > Node Definitions

Posted by Alok.Bhardwaj at 9:22 PM

Older Posts »

Propulsé par