5 avg. rating (100% score) - 2 votes
Ready to face interview for Oracle Demantra? Do not worry, we are here to help you with job interview preparation. If you are preparing Oracle Demantra interview and not sure which questions are likely asked in interview, we suggest you to go through Wisdomjobs interview questions and answers page to crack your job interview. Oracle Demantra is a tool to manage the demand and supply chain. It automatically maps the demand needed with the supplies available and the customer requirements. Using the tool, the service levels increases with low inventory costs. Strong technical skills are needed as there is huge competition. Below is the list of frequently asked Oracle Demantra interview questions and answers which gets you ready to face the interviews:
Create a C:/Tmp folder on the machine where the setup.exe will be executed prior to the installation as this will generate a log file to this folder
Note that there will also be some ancillary logs under the following folders:
Demand PlannerDatabase ObjectsOracle Server (Oracle back end database)
Demand PlannerDatabase ObjectsMicrosoft SQL Server (Sql Server back end database)
Review the Collaborator.log which is found under the …Collaboratordemantralogs folder on the web server where Demantra is running.
Also, each individual webserver (ex. OAS, JRUN, Tomcat, Websphere, etc…) will have their own individual logs in various directories which can also be consulted.
The individual webserver documentation should be reviewed for these log locations.
The key engine logs are found under the root drive of the machine where the engine is launched. The folder that holds these logs usually have Engine2k somewhere in the name.
Note that there should be at least Engine2k logs (these are the logs that show the actual splitting and forecasts that the engine does) in this folder.
However, to write the master EngineManager logs to this folder you need to go to the Engine Administrator (..Demand PlannerAnalytical Enginesbin –> Settings –> Configure) and change the Engine Manager Log tab from STD to FILE.
It is NOT advised to re-register the engine after making this change.
In general, most EBS side activities (ex. Planning Data Pull) can be logged using Note 245974.1 however, the Shipment and Bookings Collection job can have extra logging turned on by changing MSD_DEM: Debug Mode to Yes (default is No).
Note that as the Shipment and Bookings Collection job moves to the other side of the wall from EBS side of the database to the Demantra side of the database (usually indicated by when you start seeing references to the Demantra schema or tables like t_src_items_tmpl or t_src_sales_tmpl_err) then the errors may need to be tracked using the Workflow or Active_Proc_Dyn troubleshooting sections of this note.
To view the errors go to Business Modeler –> Tools –> Procedure Error Log
Note that this looks to the backend table called db_exception_log
There are three critical MOS notes that you may want to review:
When upgrading your Demantra application from an older version directly to 12.2.2, you can minimize the upgrade time. You can force parallelism using a Logon trigger on the server.
Creation of new Indexes on sales data can take long time.
As part of the upgrade there is a script building a new set of indexes, one per engine profile, on each profile quantity_form expression.
The creation of the index can take a long time on big data tables.
Remember to disable or drop that trigger when the upgrade has completed.
The following trigger was created as SYS database user and tested successfully by creating DEMANTRA database user and logging in with it:
CREATE OR REPLACE TRIGGER force_parallel_ddl_trg
AFTER LOGON ON database
IF (USER=’DEMANTRA’) THEN
EXECUTE IMMEDIATE ‘ALTER SESSION FORCE PARALLEL DDL’;
Make sure to:
Modify DEMANTRA to be the database schema name.
drop it after it is not needed anymore using the following:
DROP TRIGGER force_parallel_ddl_trg;
It depends on the context where the write error occurs:
Yes, but indirectly. The size of the Flashback Buffer is set to 2 * LOG_BUFFER.
For performance reasons, it’s recommended to set LOG_BUFFER to at least 8MB for
databases running in Flashback Mode.
UPDATE: For large 184.108.40.206+ databases with more than a 4GB SGA, you may consider setting LOG_BUFFER to values in the range of 32-64 MB.
No. Flashback Logs are not backed up. Even if the command BACKUP RECOVERY AREA is used to backup the contents of the FRA to tape only the following file types are backed up: full and incremental backup sets, control file autobackups, datafile copies, and archived redo logs.
Flashback Logs are considered to be transient files and cannot be backed up by RMAN. They are not needed for media recovery.
Flashback logs are managed by Oracle only. Oracle will try to keep as much Flashback logs as needed to satisfy the DB_FLASHBACK_RETENTION_TARGET parameter. However, if there’s space pressure in the Flash Recovery Area (FRA), flashback logs may be deleted to make room for other things, like backups and archived logs, for example.
If the fast recovery area has enough space, then a flashback log is created whenever necessary to satisfy the flashback retention target.
If a flashback log is old enough that it is no longer needed to satisfy the flashback retention target, then a flashback log is reused.
If the database must create a new flashback log and the fast recovery area is full or there is no disk space, then the oldest flashback log is reused instead.
If the fast recovery area is full, then an archived redo log that is reclaimable according to the FRA rules may be automatically deleted by the fast recovery area to make space for other files. In this case, any flashback logs that would require the use of that redo log file for the use of FLASHBACK DATABASE are also deleted.
No file in the fast recovery area is eligible for deletion if it is required to satisfy a guaranteed restore point. Thus, retention of flashback logs and other files required to satisfy the guaranteed restore point, in addition to files required to satisfy the backup retention policy, can cause the fast recovery area to fill completely.
In RMAN you can use the LIST RESTORE POINT [ALL|restore_point_name] command. If you use a recovery catalog you can use the view RC_RESTORE_POINT in the recovery catalog repository, or the command the V$RESTORE_POINT in the target database.
Yes, it’s perfectly possible.
Yes, you can. During a FLASHBACK DATABASE operation you can query V$SESSION_LONGOPS from another session to see the progress of the flashback.
The FLASHBACK DATABASE operation has two distinct phases: the actual flashback and the media recovery that happens afterwards to bring the database to a consistent state.
While the actual flashback is running you’ll see the following message in V$SESSION_LONGOPS, on Oracle 11gR2:
Flashback Database: Flashback Data Applied : 238 out of 282 Megabytes done
During the media recovery, the following messages will be seen:
Oracle’s recommendations are:
Use a fast file system for your flash recovery area, preferably without operating system file caching. It is recommended to use a file system that avoids operating system file caching, such as ASM.
Configure enough disk spindles for the file system that will hold the flash recovery area. For large production databases, multiple disk spindles may be needed to support the required disk throughput for the database to write the flashback logs effectively.
If the storage system used to hold the flash recovery area does not have non-volatile RAM, try to configure the file system on top of striped storage volumes, with a relatively small stripe size such as 128K. This will allow each write to the flashback logs to be spread across multiple spindles, improving performance
For large, production databases, set the init.ora parameter LOG_BUFFER to be at least 8MB. This makes sure the database allocates maximum memory (typically 16MB) for writing flashback database logs.
Oracle Demantra Related Tutorials
|Oracle 10g Tutorial||Oracle 9i Tutorial|
|Oracle 8i Tutorial||Informatica Tutorial|
|Oracle 11g Tutorial|
Oracle Demantra Related Interview Questions
|Oracle 10g Interview Questions||Oracle 9i Interview Questions|
|Oracle 8i Interview Questions||Informatica Interview Questions|
|PL/SQL Interview Questions||Oracle 11g Interview Questions|
|SQL Interview Questions||Oracle apps Interview Questions|
|Sybase Interview Questions||Oracle Apps ERP Interview Questions|
|Oracle 7.3 Interview Questions||Oracle Access Manager Interview Questions|
|Oracle Application Framework Interview Questions||Oracle Apps DBA Interview Questions|
Oracle Demantra Related Practice Tests
|Oracle 10g Practice Tests||Oracle 9i Practice Tests|
|Oracle 8i Practice Tests||Informatica Practice Tests|
|PL/SQL Practice Tests||Oracle 11g Practice Tests|
|SQL Practice Tests||Oracle apps Practice Tests|
|Sybase Practice Tests||Oracle Apps ERP Practice Tests|
|Oracle 7.3 Practice Tests|
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.