Friday, 2 June 2017

Custom apps read only schema concepts

Dear Friends,

Today, we will learn about custom schema or read only schema creation. Many people ask about custom schema and it’s really very important also. If you are a DBA and you have knowledge and hands-on on CUSTOM things in apps, it will be very useful anywhere in companies. You will get high priorities and you will be having high demands in market.

Actually, I would like to tell one more thing, why we need custom? Why we create it? What we can do with Custom? There are many such questions, which can be arising person to person.

Everyone has different thinking and thoughts.

If you have experiences in DBA then any interviewers will ask a question about Custom. Either do you know custom or have you worked on custom?

Even if you ask me frankly, it was asked by me also in interviews for oracle.
So, let’s come to the points now.

Actually, Custom schema is like you are creating the extended version of the standard schema(s) if it is limited your directory needs.

Some important points which we should keep in mind while creating the Custom Schema such as:

We should minimize the mandatory attributes.

We should reuse existing schema elements if possible.

We should not define more than one object class or attribute for same purpose.

Always try to keep the schema simple as much as possible.

Note: While customizing the schema, never delete, modify or replace any existing definitions of attributes or object class in standard schema. It may create problem for future. By doing so, we can face issue such as with other directories and with LDAP client applications.

Some common tips for naming or creating objects are following:

You create object class as shown below:

Our mistake: We create object class as ObjectClass.

But we should always follow standard as extensibleObject or customObject.
So, by seeing only anyone can understand that is it custom.

Below are the two approaches to creating new object classes:

1. Create many new object classes, one for each object class structure to which you want to add an attribute.

2. Create a single object class that supports all of the attributes that you create for your directory. You create this kind of an object class by defining it to be an AUXILIARY object class.


Some more useful links:

R12.2 Architecture and Concepts

R12.2 Adop Patching

PRVF-0002: 12c Database issue andSolution

Career Planning Tips

How to Rotate Log file in Linux

Hope this may useful and helpful. For any concerns or suggestions, please write to us either in comment box or Contact Us


No comments:

Post a Comment

Thank you for your comments and suggestions. It's good to talk you.