This link is quite insightful and informative highlighting poor implementations of big and famous.It re-inforces the beilief that success / failure of an ERP project is more that of people on the project than that of the product itself . Happy reading....

All in for ERP is a Blog where it's all about Infor and it's ERP system Infor LN. It's provided by Ulrich Fuchs, a freelance consultant with two decades of experience in implementing Infor's ERP systems.

Amazing tools are available in MS Excel 2007 & Above Ver... .....................................................................................................If we know VBA & SQL then we can do anything in EXCEL VBA,

that i can develop any type of report for MIS in this tools.......................................................................................................This tool is very user friendly & not required any type of reporting tools.......................................................................................................

About the instructor

A number of books and manuals suggest a backup schedule for Oracle databases in archivelog mode something like, daily hot (online) backups and weekly cold backups. What is strange about this recommendation is that the weekly cold backups serve no apparent purpose, other than to needlessly remove the instance or instances from service for some period of time. Shutting the database down for a cold backup also has the side effect of requiring the buffer cache be reloaded all over again after startup, which degrades performance while all reads are initially physical for a period of time.

Many guides to backup and recovery give the Export and Import utilities billing equal to physical backup methods. As a method, Export and Import provide uniformly inferior reliability on backups, as well as recoveries. In addition to being failure prone, mean time to recovery with Import is much longer than comparative recoveries using physical backups. Export creates dump files that contain the DDL for all objects and the table data in the database.

During an Oracle tablespace hot backup, a script or program puts a tablespace into backup mode, then copies the datafiles to disk or tape, then takes the tablespace out of backup mode. Although these steps are widely understood, the idea that datafiles are not written during backup mode is probably the most alarming and widely held misconception about Oracle. So many people think this is true, that it is actually asserted as fact in the backup/recovery sections of a number of major published books on Oracle.

In order to be sure that all changes generated during a hot backup are available for a recovery, Oracle recommends that the current online log be archived after the last tablespace in a hot backup is taken out of backup mode. A similar recommendation stands for after a recovery manager online database backup is taken. A wide variety of literature on backup and recovery, including the oracle documentation, suggests using the

If an instance crashes or is aborted while one of the tablespaces is in backup mode, the tablespace(s) will appear to need media recovery upon startup. In normal instance failure situations, automatic crash recovery using the online redologs will be automatically performed, with no intervention required.