When projects transition to production, the receiving team need some transition documentation to help with knowledge transfer and to guide them while they get accustomed to operating the application and can form their own documentation. This temple is shell, which usually provides enough detail, with some updating, to provide a quick reference regarding the application. Also, having a temple can be a real time saver, as opposed to writing it from scratch.
What is BYOD?
Basically, BYOD (bring your own device) is an information technology trend toward employee-owned devices within a business, in which consumer software and hardware are being integrated into the enterprise workplace.
Benefits of BYOD
The benefits of BYOD depend upon the point of view, here is a quick list
- Supports integrated remote work and remote workforce augmentation with requiring the acquisition of hardware and software
- Reduced software learning curve for employees
- Increased availability of work force and access to network.
Drawbacks of BYOD
- Increased Support requirements
- Increase Security and data exposure risk
- Less consistent hardware and Software environment
Sometimes there is a need to find and/or kill (terminate) table locks, so, that application process and user access can be restored. To do this relative straight forward if you have access and the appropriate permission to the Netezza PureData server.
How to find table locks on a Netezza database
- Log into the Netezza server
- From the command line, navigate to Netezza directory (e.g. cd /NZ)
- On the command line enter show locks command
Show Locks Command (nz_show_locks) Syntax
nz_show_locks <db name> <tablename>
Example Show Locks Command (nz_show_locks)
nz_show_locks dashboard_staging stg_nz_query_history
How to kill table locks on a Netezza database
- Perform find locks above
- Then, on the command line enter kill sessions locks command
Kill Sessions Command (nzsession) Syntax
nzsession subcmd [subcmd options]
Example Kill Sessions Command (nzsession)
nzsession abort -id 523662 -force
First let us start with dispelling a common myth, The InfoSphere scheduler is not an Enterprise Scheduler application.
The scheduling service in InfoSphere leverages the operating system (OS) scheduler, in the case of Linux this is CRON, and provides graphical User Interface, which a provides time based capability to schedule Jobs at the Suite component level. The Director Client scheduler can:
- Schedule individual jobs and sequence jobs
- Schedule Jobs/Sequencers to run:
How to set-up the Daily Schedule
Steps to set the Daily Schedule are below:
- Open the DataStage Director
- Once the browser is open click on Job>Add to Schedule
- Click “Daily” under the “Run Job” and choose the time
The term system availability, in a nutshell, describes a system operating correctly, reachable, and is available for use by consuming customer and systems. Generally, speaking system availability is a measure used to ensure that a system and/or application is meeting it Service Level Agreement (SLA) obligations. Any loss of service, whether planned or unplanned, is known as an outage. Downtime is the duration of an outage measured in units of time (e.g., minutes or hours).
What is a Runbook?
What is a Runbook: a runbook is a collection of procedures, instruction, and operations used for reference (like Standard Operating procedures), which systems administrators or operations teams perform in the normal course of monitoring, controlling, and orchestrating technical systems and process.
Assuming that your InfoSphere instance has been installed and configured, here is a quick migration checklist to assist in making sure that you have performed the essential tasks.
|Major Tasks||Parent-Tasks||Child-task||Completion Status|
|Create Migration Package|
|Create Database scripts|
|Export DataStage components|
|Gather support files|
|Compress migration package|
|Baseline migration package in CM Tool|
|Upload package to target environment|
|Deploy Database Components|
|Backup target databases|
|Deploy database components|
|Resolve script errors|
|Create JDBC, ODBC, and/or TNSNAMES entries|
|Install and Configure RDBMS client on Infosphere server|
|Load configuration and conversion data (if not loaded by ETL)|
|Deploy Support Files|
|Create File Structures|
|Surrogate Key Files|
|System Administration Scripts|
|Node Configuration Files|
|Deploy DataStage Components|
|Create Project (if required)|
|Configure Project and/or Project Parameters (if required)|
|Import ETL’s into DataStage|
|Update Parameters and Parameter sets (if required)|
|Update job properties|
|Compile ETL using Multiple Job Compile|
|Resolve compilation errors|
|Finalize CM Baseline|