Weblogic startup hanging

I’ve encountered this before but somehow keep on forgetting. When booting up weblogic and it started to hang, it is normally caused by corrupted datafiles under /domains/<domain name/servers/AdminsServer/data

Deleting the data directory should resolve the issue. Don't worry as the directory gets recreated during startup

Windows insider Experience


Enrolled myself to the windows insider program and was able to take the new Microsoft OS for a spin. Initially tested the release on Oracle Virtual box, installation went smoothly.

I then  decided to jump the gun and upgrade my windows 8.1 on my acer iconia w700 to windows 10 release, installation was a success but errors were encountered left and right, a bit expected and waited for a new build to be released.

Proceed with the upgrade of windows 8.1 to windows 10 mobile on my lumia 920. Corrupted my OS, have to plugin to my PC to perform recovery. Was able to recover and install, my lumia 920 is now running windows 10 preview.

A new windows 10 build was released, upgraded my windows 10 VM first. Seen a lot of improvement. Upgraded my w700, Encountered a boot loop issue. I have to reformat my w700 and reinstall windows 8.1 then upgrade to windows 10 build. This time the upgrade works and a more stable windows 10 runs smoothly on my w700. Impressed with the UI and the performance.

Signup for the August 29 windows 10 release on my asus laptop.the same laptop which host my Windows 10 VM.

Dday, August 29. Downloaded windows 8.1 upgrade on my PC which took about an hour or so. After the download and install. Windows 10 start downloading and was able to upgrade my asus from windows 8.1 to 10

Still testing, my setup are as follows:

1. Windows 10 preview on Oracle virtual box 5, guest OS on asus gaming laptop

2. Windows 10 home on ASUS gaming laptop

3. Windows 10 professional on my afer iconia w700 touch

4. Windows 10 mobile preview on my Lumina 920

System integration

Like many enterprise application. Many companies are very much liberal in the installation and deployment guide that they normally published specially for products requiring large scale installations and integrations. After all, it is hard to account for multiple scenarios that can take place on the implementing side of the fence. Due dilligence should be made and fingers cross the approach you’ve chosen works! At the end of the day, you can’t test every possible scenario anyway.

Oracle VM virtual box 5

Back in the days dual booting OS is a “in” thing. Yes i belong to that generation. I’ve been playing around with virtual machine for quite sometime using Oracle VM. It’s open source and free for those who like to play around with virtualization, OSes and networking. To date i have around 9 VMs configure in the machine i’m using

Version 5 were recently released and can be downloaded on the following url: https://www.virtualbox.org/

not forgotten

been busy with work lately but you are not forgotten. currently working on other Oracle product besides peoplesoft as part of the project requirements. Embrace the change yay! I’ll find some time to update this blog with some of the stuff i’m working on

PS/NVision with Active Data Guard

Active Data Guard(ADG) is one of the key feature introduced in PeopleTools 8.51, steps to configure ADG is discussed in the Peoplebooks Data Management section:


I made the recommendation to configure ADG in order to maximize the PeopleTools 8.53 feature as part of an Ongoing Upgrade project. Besides the PeopleTools documentation, it is also one of the highlight in the Release value proposition for PeopleTool 8.53 especifically the ability to offload processing to standby database via ADG. Imagine my surprise when we raise an SR to oracle to address an issue we are encountering when running PS/nVision on the standby database and was advised that the functionality is not supported by ADG contradicting the previously published document.

Not entirely convinced by the information provided, I performed some troubleshooting and managed to make PS/nVision run against the standby database. It turned out that additional process are required besides the one outlined in PeopleBooks. The highlevel wil be:

1. create DBlink- script provided by oracle createdblinktoprimary.sql
2. create local synonyms- scripts provided by oracle createlocalsynonyms.sql
3. create remote synonyms- scrips provided by oracle createremotesynonyms.sql

The missing steps for DML redirection requires a trigger to be created which switch the primary schema user to standby schema user each time it login to the standby database. The details can be found in


classic imp/exp vs datapump

To maintain environment configuration, we are using the classic oracle imp/exp process to extract and load data from and to the database. Datapump as oracle presents it is an improvement to the classic imp/exp and is known to be fast in comparison. This seems to be a good CI for the existing process however after trying out the tool, i discovered that impdp/expdp will actually not allow you to perform the extract/load of tables outside the database host. something that can be done with imp/exp.

overall, i’m disappointed and is now working on tuning the imp/exp process instead.

PeopleSoft Integration Broker exploit

We had an incident recently involving integration broker(IB) node on production environment getting updated without performing modification on both online and the IBconfig.properties file. I’m not sure if other user encountered similar issue but i would say it can actually occur if you are maintaining multiple peoplesoft environment and has something to do with how Peoplesoft maintains the IB node configuration.

To recreate the issue/scenario encountered, you can perform the following steps:
1. you will need 2 peoplesoft environment. one to perform the change(source) and another which you want to keep intact(target).

2. login to source and navigate to IB Gateway configuration page. update or create a new Gateway using the target url as the Gateway properties. Save changes.

3. again on the source, navigate to the IB node configuration and perform changes on the IB node. First, ensure that the IB node is using the Gateway that was updated or created in step 2. Then update the IB node configuration by adding additional appserver, etc. Save and ping the IB node.

5. Finally, login to your target environment and verify if there are any changes in the IB node settings.

While updating IB node requires password to be provided, it is important to note that IB node is connected to the Gateway properties. Any update to the IB node which uses the gateway will reflect on the target environment instead of the source.

While this can be avoided by ensuring that the Gateway/IB node setup are not shared across multiple environment unless required as part of integration. I can see similar issue occurring specially around database refreshes/cloning.