BlueStudios Johns Blog

Its Just another WordPress weblog.. Really!

Archive for January, 2009

Wednesday
Jan 21,2009

For anyone out there tracking bugs with Oracle -
here’s some info of how to track them and find out what the status actually means ;)

My Oracle Support -
1. Enter the Bug number in the upper right “Search Knowledge Base” field.
2. Select the magnifying glass icon.
3. Select the bug’s hyper-linked summary.
4. In the resulting right-pane summary, select the “star” icon to add the bug to your Favorites.
5. Monitor periodically by either the Bug Summary pane (can be added to your Dashboard via the “Customize Page” upper right main page link) or via the “Favorites/Bug” upper right main page drop down).

Classic MetaLink -
1. Select Document ID (Knowledge Base, Forum or Bug) in the Quick Find dropdown list.
2. Enter the Bug number in the text field.
3. Select “Go”.
4. The bug number and subject appear.
5. Select on the bug number in the results window.
6. Select on Bookmark.
7. Monitor periodically by clicking My Headlines then the Bookmarks button.

Bug Status Info -
10 – Description Phase:
Development is requesting more information.
16 – Support bug screening:
Bug is being reviewed by our Bug Diagnostics group.
11 – Code Bug (Response/Resolution):
Bug is being worked by Development.
30 – Additional Information Requested:
Bug is being worked by Support and/or more information was requested by Development.
37 – To Filer for Review/Merge Required:
Bug has been fixed but the patch will be merged into the next patchset.
74 – Closed, Verified by QA:
Bug verified by Quality Assurance team.
80 – Development to Q/A:
Bug is being regression tested for future release.
81 – Q/A to Dev/Patch or Workaround Avble:
Patch released via My Oracle Support/Classic Metalink.
90 – Closed, Verified by Filer:
Bug has been fixed and is closed.
91 – Closed, Could Not Reproduce:
Bug is closed as not reproducible.
92 – Closed, Not a Bug:
Bug is closed as not a bug (not reproducible or setup issue).
93 – Closed, Not Verified by Filer:
Bug has been fixed and is closed.
95 – Closed, Vendor OS Problem:
Bug is closed as an OS problem.
96 – Closed, Duplicate Bug:
Bug is closed as a duplicate bug.

The status numbers indicate the progress being made on the bug.
When you see the bug status change to status 74 or 81, that means the patch has been released.

Tuesday
Jan 20,2009

Ok, as we all know, Stellent were never that great with Documentation.. .. ..
Just try asking for support with SSPU or asking for the JavaScript API documentation.. ;)

Because of this I’m going to start creating a list and maybe if I get some time, I`ll build a small reference library for people to search through. Maybe even with AIR ;) oooh…

So here are the first set of fields I`ve managed to find that I could not find any reference too-

ClientEncoding=UTF8
Set Contributors Encoding Type.

InternalUpload=true
DIS config to specify location of primary files without browse option.
Displays as text field.

IdcClientPersistFields=coreContentOnly
Not Sure if this stores a cookie.. But its a good way to keep variables persistantly stored whilst navigating around the UCM try adding this to the URL – IdcClientPersistFields=coreContentOnly&coreContentOnly=1

I haven’t been able to get this to work as yet within 10gR3? and not sure as yet if it accepts multiple fields seperated with a comma ‘,’ ie IdcClientPersistFields=coreContentOnly,myVar&coreContentOnly=0&myVar=myValue

Saturday
Jan 17,2009

So recently I have come up against a problem..
Tooo many users are interacting with the content server causing a lot of timeouts..

To fix this I increased the number of DB connections; heres how -

1. Goto <content server>\config directory.
2. Open the config.cfg in a text editor.
3. Add the following setting to the config.cfg file and save the file:
NumConnections=25
5. Restart the server