Thursday, August 25, 2016

Monday, July 13, 2015

Saturday, March 14, 2015

APEX-Tabula Form: Using built-In Wizard




1.Create a Blank  Page
            [ ID=501  , Name=fee information ]


2: Creating Region
  Page Rendering> Region{ Create}>form>Tebular >

                                * Table> FEE
                                * Primary Key Value=> PL/SQL Program

DECLARE
   L_PRIMARY_KEY NUMBER;
BEGIN
   SELECT nvl(MAX(fee_Id),100) + 1
   INTO   L_PRIMARY_KEY
   FROM  fee;

   RETURN L_PRIMARY_KEY;
END;


3.Trigger for Primary Key Value  [ Optional ]

 create or replace trigger  trg_fee_bi
 before insert on fee
 for each row
begin
     SELECT nvl(MAX(fee_Id),100) + 1  INTO  :new.fee_id  FROM  fee;
end;

Friday, March 13, 2015

Apex-List: For User Home Page



1.Creating List

Application> Shared Component> List >[ Create ]

    * > From Scratch > [ Name: FEE_COLLECTOR  , Type: Static ]

           Label                       page
         --------------------------------
          Fee Name                501
         Course Name           503
         Department              505

2. Attaching Image within List
      Application> Shared Component> List > click on FEE_COLLECTOR

           * > Click on item [ fee Name ] > select image  [  APPLY Change ]


3.Create a Blank Page
          [ ID=500  , Name= User Home Page ]

4.Create a region [ type List ]
        Type=List
        Template=>Horizontal image with label List


5. To Navigated Page [ example:  501= Fee Names ]
    * Create a region BACK Button
                         [  Position: right of the page title ,
                            Action: =Redirect to page
                            Page:  500 ]


Saturday, February 28, 2015

APEX-Region SQL



Page rendering > Region > create > reports > Classic Reports >

Monday, February 16, 2015

Apex-DML: Manual FORM Style




1.Database Table
----------------------
create table personal_info
(id  number(5),
 pname       varchar2(100),
 gender      varchar2(1),
 married     varchar2(1),
 smoker      varchar2(1),
DOB         date,
country     varchar2(100)
);

2.Create a bank page / Create a HTML Region / Create below Items
----------------------------------------------------------------------------------
   id    ---pk value
   pname  -- text item
   gender -----list item
    married  ---radio item
    smoker   --- check box
    country  --- pop up list


 3.Sending Data to Database Table=personal_info
--------------------------------------------------------------
    * create a region button names=> ADD < action submit>
    * create a process named=> PRC_ADD
                    < Process Point: On submit : before computation and validation >
                    <Source>


   BEGIN
      Insert into personal_info(id,pname,gender,married,smoker,dob,country)
      values(:P101_ID,:P101_PNAME,:P101_GENDER,:P101_MARRIED,:P101_SMOKER,:P101_DOB,:P101_COUNTRY);

        commit;
  END;






Use Below Reference
----------------------
https://tts.inso.tuwien.ac.at/i/doc/bldapp_frm_manual.htm

Apex-Login:Custom






http://djmein.blogspot.com/2007/07/custom-authentication-authorisation.html


https://docs.oracle.com/cloud/latest/db112/HTMDB/GUID-6441782B-12E4-4465-B2A4-216141A4AAA7.htm#HTMDB12003

Tuesday, March 19, 2013

Backup AND Recovery // Best Practices For Enterprise Data


Data warehouses hold data that originate from countless range of sources, which are transformed before inserting into a database. Managing the recovery of a large data warehouse can be a daunting task and traditional OLTP backup and recovery strategies may not meet the needs of a data warehouse.
A backup strategy should be planned during the system design phase, focusing more on what to backup and frequency of the same. The amount of resources available to perform a backup or a recovery; and the recovery time objective (the amount of time one can afford the system or part of the system to be unavailable) are two most important variables that need to be focused upon while planning a backup and recovery strategy.
NOLOGGING operations must be taken into account when planning a backup and recovery strategy. Traditional recovery, restoring a backup and applying changes from the archive log, do not apply for NOLOGGING operations.  Above all, watch out for failure of subsequent operations, that rely on the data manipulated by this operation. Never make a backup when a NOLOGGING operation is taking place. Plan for one of the following or a combination of the following strategies:
The ETL strategy. Recover a backup that does not contain non-recoverable transactions and replay the ETL that has taken place between the backup and the failure.
The incremental backup strategy. Perform a backup immediately after an otherwise non-recoverable transaction has taken place. Oracle provides a tracking file feature that enables incremental backups based on changed data blocks. RMAN leverages the tracking file feature.
Strategies for Backup and Recovery
Planning a backup and recovery strategy can be a challenging task; especially when there are huge gigabytes of data that need to be immunized from all the virtual and dynamic threats. The following practices can help you implement your warehouse’s backup and recovery strategy:

Blink consulting is a premiere management consulting and technology company that facilitates organizations to achieve their business goals while maximizing value from their investments. Headquartered in Boston we are an Oracle gold partner working with a zeal to provide innovative, integrated and productive solutions to dynamic enterprises. We provide Flexible solutions in Data recovery and Backup along with Oracle e-business suite implementation services.

Wednesday, March 13, 2013