Mostrando entradas con la etiqueta #DB2. Mostrar todas las entradas
Mostrando entradas con la etiqueta #DB2. Mostrar todas las entradas

jueves, 25 de junio de 2015

DB2 BACKUP OF THE DATABASE

Sometimes a backup of the Database is required,

with this in mind, Imgoing to show you the steps to do a DB2 backups in DB2

step 1

you need to execute the following query, adapting  to your database and the filesystem to do the backup

CONNECT TO ECMDB;
QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS;
CONNECT RESET;
BACKUP DATABASE ECMDB TO "D:\DB2 Backup\240615" WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT PROMPTING;
CONNECT TO ECMDB;
UNQUIESCE DATABASE;





CONNECT RESET;CONNECT TO ECMDB;
QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS;
CONNECT RESET;
BACKUP DATABASE ECMDB TO "D:\DB2 Backup\240615" WITH 2 BUFFERS BUFFER 1024 PARALLELISM 1 WITHOUT PROMPTING;
CONNECT TO ECMDB;
UNQUIESCE DATABASE;
CONNECT RESET;

martes, 23 de junio de 2015

INPUT OUTPUT DB2 TRY & REMOTE:OFFICE NOT REQUIRED JASON FRIED


n’t have time to read? Here’s a quick but comprehensive summary of  “Remote: Office Not Required” by Jason Fried and David Heinemeier Hansson, released on October 29, 2013.
Who should read this: Companies or employees who are considering remote work or already doing it.
Elevator pitch: Remote lays out the argument for remote work and teaches you how to maximize productivity and happiness as an employee and an employer.
Author: Jason Fried and David Heinemeier Hansson are the cofounders of37signals and authors of Rework. Heinemeier Hansson is also the creator of the popular Ruby on Rails framework.

Benefits 

Advances in technology – like file and screen sharing, to-do lists, and instant messaging – have made remote work more feasible than ever.
For employers: Employers may find that employees (especially creatives) are more productive when they aren’t subject to in-the-office interruptions. While remote work has its interruptions, most of them are voluntary – you choose to check Facebook or get a snack.
Although not the main goal, remote work allows employers to cut down on office space costs. You don’t have to worry about whole offices being struck by natural disasters or power outages; employees who might take time off for various reasons can work from home instead.
Remote work exposes bad workers: it’s easy to see who’s not performing without the obscuring fog of in-person charisma.
For employees: Employees get judged on their results, not their input (hours worked) or other irrelevant factors. Remote work cuts back on commuting and gives employees the freedom and time to pursue passions that they might otherwise put off until retirement. It allows people to work whatever hours they want, from whatever part of the country they want. Employees save money on gas and can spend more time with family.

Drawbacks and critiques

Remote work does have its drawbacks: no face-to-face interaction, the temptation to procrastinate is higher, and family members can be distracting.
Employers worry that remote work means less frequent brainstorming and slower communication, but that may actually be beneficial. As for worries of employees slacking off and being distracted, the solutions is to hire people you trust.
Employers worry that remote work will harm culture, but culture is more about values and actions rather than social activities.
Employers worry about security, but there are simple steps to take to secure employees’ personal computers.
Employers worry about having customer service agents available during business hours, and this is a valid question. Customer service staff can stagger their hours so 9-5 is covered, but even if they don’t, that doesn’t mean the whole company must go 9-5. Different roles call for different responsibilities.
Employers claim that big corporations don’t have remote work, which is only partly true. And even so, corporations aren’t exactly bastions of efficiency.
Finally, employers give a variety of silly excuses that are easily refuted by facts and common sense: it doesn’t work for our industry, managers will lose control, and the office cost a lot of money. The gains in productivity from remote work across many industries should be response enough.

Tips for collaborating remotely

  • Try to make sure that employees on different time zones have about four hours of overlap in working hours.
  • Use screenshots or screencasts to communicate information.
  • Share information openly on work schedules, to-do’s, calendars, and files.
  • Create a “virtual water cooler,” a chat forum for fun and social stuff.
  • Share progress with each other to fuel that sense of achievement and momentum.
  • Consider a hybrid strategy, with some employees working in the office and some at home. (37signals has a Chicago office with about 10 people, while the other 26 are spread across the world.)
  • Don’t only try one remote worker – try at least a team.

Handling common issues

Employees: To deal with cabin fever, make sure to take time to go out and socialize, or consider working from a coworking space. To avoid hurting yourself, set up a work area according to proper ergonomics. To avoid a sedentary lifestyle, take time to exercise and eat well.
Employers: To convince clients to work with you remotely, be honest up front about your location, offer references, share progress often, respond promptly, and get the client involved. To make sure you’re complying with the law, consult a lawyer or accountant about out-of-state workers. For international employees, you’ll have to either establish an office in that country or hire them as consultants.

Hiring remote employees

To find the best people, look internationally. Favor real work over resumes to evaluate candidates. Meet top candidates in person to check for personality fit.
Pay employees equally across geographies to improve retention and show you value them. To keep morale up, everyone has to work extra hard on communicating well in writing and not offending others.
To make up for the distance, get to know your employees as individuals and experiment with creative ways to support their hobbies and interests.

Managing remote workers

To set up remote work, start it as early as possible in the life of your company; if you’re already in business, offer the remote work option to current employees. As a manager, you’ll have to be comfortable with giving employees more access to information and more decision-making ability, and focus on leading, guiding, and helping with problems that come up. Face-to-face and in-person meetups will become more scarce but more valuable: try a few yearly in-person meetups, and one-on-one check-ins every few months. Watch out for remote workers feeling inferior or underserved, and for them overworking and burning out.

Life of a remote worker

To prevent overwork, try creating separation between work and play with different clothes, spaces, or times. Experiment with different setups: working remotely only in the morning, working at public places like coffee shops, or renting a desk at a local office. Speak up if you’re feeling unmotivated, and get attention by being productive.

Grade: A-

In 37signals style, Remote is incredibly digestible – more a collection of short blog posts than a series of thick chapters. If you’re a remote worker, you’ve probably already figured out many of the insights in the book, but you’ll undoubtedly be able to find a few takeaways. (I myself realized I had an email addiction and forced myself to get out of my inbox for one evening – it’s a start.) The value may be even greater for employees considering remote work, or employers who are trying to manage it. One of the biggest lessons is how important communication becomes – staying positive in your emails, being honest about a lack of motivation or burnout, and making sure everyone knows what everyone else is doing – and that’s something we could all use a refresher on.

DB2 SCRIPT DATABASE
INPUT:

-- *****************************************************************
--                                                                
-- Licensed Materials - Property of IBM                            
--                                                                
-- 5724-U69                                                        
--                                                                
-- Copyright IBM Corp. 2012  All Rights Reserved.                  
--                                                                
-- US Government Users Restricted Rights - Use, duplication or    
-- disclosure restricted by GSA ADP Schedule Contract with        
-- IBM Corp.                                                      
--                                                                
-- *****************************************************************
--
-- IBM Content Navigator configuration table creation script
-- for DB2 LUW
-- *****************************************************************
--  Create a schema for the application to use
CREATE SCHEMA ECM_SC;
-- *****************************************************************
--  Create buffer pools and tablespaces for the application to use
CREATE Bufferpool ECM_TSBP IMMEDIATE SIZE 200 PAGESIZE 32K;
CREATE Bufferpool ECM_TSTEMPBP IMMEDIATE SIZE 200 PAGESIZE 32K;
CREATE REGULAR TABLESPACE ECM_TS PAGESIZE 32 K
MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 20 M
INCREASESIZE 20 M BUFFERPOOL ECM_TSBP;
CREATE USER TEMPORARY TABLESPACE ECM_TSTEMP PAGESIZE 32K
MANAGED BY AUTOMATIC STORAGE BUFFERPOOL ECM_TSTEMPBP;
-- *****************************************************************
--  Create the configuration table for the application to use
SET CURRENT SQLID = ECM_SC;
CREATE TABLE CONFIGURATION (
        ID VARCHAR(256) NOT NULL,
        ATTRIBUTES DBCLOB(32k),
 PRIMARY KEY(ID)
    )
    DATA CAPTURE NONE IN ECM_TS;
ALTER TABLE CONFIGURATION VOLATILE;
-- *****************************************************************
--  Grant privileges on the table to the JDBC connection user
GRANT INSERT, DELETE, UPDATE, SELECT, INDEX ON TABLE CONFIGURATION TO USER ADMINISTRATOR WITH GRANT OPTION;
GRANT CONTROL ON TABLE CONFIGURATION TO USER ADMINISTRATOR;
-- *****************************************************************
--  Load the initial application configuration into the table
INSERT INTO ECM_SC.CONFIGURATION VALUES ('application.navigator', 'locales=ar,he,en,zh_CN,zh_TW,cs,hr,da,nl,fi,fr,de,el,hu,it,ja,ko,nb,pl,pt,pt_BR,ru,sk,sl,es,sv,th,tr,ro;threadSleepTime=5;plugins=;menus=;repositories=;desktops=admin;viewers=default;servers=cm,od,p8,cmis;key=871bf66c911f811fd48a6cc97aea40a4;objectExpiration=10;desktop=default');
INSERT INTO ECM_SC.CONFIGURATION VALUES ('settings.navigator.default', 'mobileAccess=true;logging.level=2;logging.excludes=com.ibm.ecm.configuration;iconStatus=docHold,docNotes,docMinorVersions,docDeclaredRecord,docBookmarks,docCheckedOut,workItemSuspended,workItemDeadlineImportance,workItemDeadlineReminderSent,workItemLocked,workItemCheckedOut;adminUsers=svc-fn1d01');
INSERT INTO ECM_SC.CONFIGURATION VALUES ('desktop.navigator.admin', 'authenticationType=1;workflowNotification=false;fileIntoFolder=false;showSecurity=false;viewer=default;theme=;name=Admin Desktop;isDefault=Yes;menuPrefix=Default;applicationName=IBM Content Navigator;configInfo=;layout=ecm.widget.layout.NavigatorMainLayout;defaultFeature=ecmClientAdmin;actionHandler=ecm.widget.layout.CommonActionsHandler;servers=cm,od,ci,p8,cmis;repositories=');




OUTPUT:
------------------------------ Commands Entered ------------------------------
connect to ECMDB user ADMINISTRATOR using ********;
------------------------------------------------------------------------------
connect to ECMDB user ADMINISTRATOR using        

   Database Connection Information

 Database server        = DB2/NT64 9.7.10
 SQL authorization ID   = ADMINIST...
 Local database alias   = ECMDB


A JDBC connection to the target has succeeded.
------------------------------ Commands Entered ------------------------------
-- *****************************************************************
--                                                                
-- Licensed Materials - Property of IBM                            
--                                                                
-- 5724-U69                                                        
--                                                                
-- Copyright IBM Corp. 2012  All Rights Reserved.                  
--                                                                
-- US Government Users Restricted Rights - Use, duplication or    
-- disclosure restricted by GSA ADP Schedule Contract with        
-- IBM Corp.                                                      
--                                                                
-- *****************************************************************
--
-- IBM Content Navigator configuration table creation script
-- for DB2 LUW
-- *****************************************************************
--  Create a schema for the application to use
CREATE SCHEMA ECM_SC;
-- *****************************************************************
--  Create buffer pools and tablespaces for the application to use
CREATE Bufferpool ECM_TSBP IMMEDIATE SIZE 200 PAGESIZE 32K;
CREATE Bufferpool ECM_TSTEMPBP IMMEDIATE SIZE 200 PAGESIZE 32K;
CREATE REGULAR TABLESPACE ECM_TS PAGESIZE 32 K
MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 20 M
INCREASESIZE 20 M BUFFERPOOL ECM_TSBP;
CREATE USER TEMPORARY TABLESPACE ECM_TSTEMP PAGESIZE 32K
MANAGED BY AUTOMATIC STORAGE BUFFERPOOL ECM_TSTEMPBP;
-- *****************************************************************
--  Create the configuration table for the application to use
SET CURRENT SQLID = ECM_SC;
CREATE TABLE CONFIGURATION (
        ID VARCHAR(256) NOT NULL,
        ATTRIBUTES DBCLOB(32k),
 PRIMARY KEY(ID)
    )
    DATA CAPTURE NONE IN ECM_TS;
ALTER TABLE CONFIGURATION VOLATILE;
-- *****************************************************************
--  Grant privileges on the table to the JDBC connection user
GRANT INSERT, DELETE, UPDATE, SELECT, INDEX ON TABLE CONFIGURATION TO USER ADMINISTRATOR WITH GRANT OPTION;
GRANT CONTROL ON TABLE CONFIGURATION TO USER ADMINISTRATOR;
-- *****************************************************************
--  Load the initial application configuration into the table
INSERT INTO ECM_SC.CONFIGURATION VALUES ('application.navigator', 'locales=ar,he,en,zh_CN,zh_TW,cs,hr,da,nl,fi,fr,de,el,hu,it,ja,ko,nb,pl,pt,pt_BR,ru,sk,sl,es,sv,th,tr,ro;threadSleepTime=5;plugins=;menus=;repositories=;desktops=admin;viewers=default;servers=cm,od,p8,cmis;key=871bf66c911f811fd48a6cc97aea40a4;objectExpiration=10;desktop=default');
INSERT INTO ECM_SC.CONFIGURATION VALUES ('settings.navigator.default', 'mobileAccess=true;logging.level=2;logging.excludes=com.ibm.ecm.configuration;iconStatus=docHold,docNotes,docMinorVersions,docDeclaredRecord,docBookmarks,docCheckedOut,workItemSuspended,workItemDeadlineImportance,workItemDeadlineReminderSent,workItemLocked,workItemCheckedOut;adminUsers=svc-fn1d01');
INSERT INTO ECM_SC.CONFIGURATION VALUES ('desktop.navigator.admin', 'authenticationType=1;workflowNotification=false;fileIntoFolder=false;showSecurity=false;viewer=default;theme=;name=Admin Desktop;isDefault=Yes;menuPrefix=Default;applicationName=IBM Content Navigator;configInfo=;layout=ecm.widget.layout.NavigatorMainLayout;defaultFeature=ecmClientAdmin;actionHandler=ecm.widget.layout.CommonActionsHandler;servers=cm,od,ci,p8,cmis;repositories=');
------------------------------------------------------------------------------
CREATE SCHEMA ECM_SC
DB20000I  The SQL command completed successfully.

CREATE Bufferpool ECM_TSBP IMMEDIATE SIZE 200 PAGESIZE 32K
DB20000I  The SQL command completed successfully.

CREATE Bufferpool ECM_TSTEMPBP IMMEDIATE SIZE 200 PAGESIZE 32K
DB20000I  The SQL command completed successfully.

CREATE REGULAR TABLESPACE ECM_TS PAGESIZE 32 K MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 20 M INCREASESIZE 20 M BUFFERPOOL ECM_TSBP
DB20000I  The SQL command completed successfully.

CREATE USER TEMPORARY TABLESPACE ECM_TSTEMP PAGESIZE 32K MANAGED BY AUTOMATIC STORAGE BUFFERPOOL ECM_TSTEMPBP
DB20000I  The SQL command completed successfully.

SET CURRENT SQLID = ECM_SC
DB20000I  The SQL command completed successfully.

CREATE TABLE CONFIGURATION ( ID VARCHAR(256) NOT NULL, ATTRIBUTES DBCLOB(32k), PRIMARY KEY(ID) ) DATA CAPTURE NONE IN ECM_TS
DB20000I  The SQL command completed successfully.

ALTER TABLE CONFIGURATION VOLATILE
DB20000I  The SQL command completed successfully.

GRANT INSERT, DELETE, UPDATE, SELECT, INDEX ON TABLE CONFIGURATION TO USER ADMINISTRATOR WITH GRANT OPTION
DB20000I  The SQL command completed successfully.

GRANT CONTROL ON TABLE CONFIGURATION TO USER ADMINISTRATOR
DB20000I  The SQL command completed successfully.

INSERT INTO ECM_SC.CONFIGURATION VALUES ('application.navigator', 'locales=ar,he,en,zh_CN,zh_TW,cs,hr,da,nl,fi,fr,de,el,hu,it,ja,ko,nb,pl,pt,pt_BR,ru,sk,sl,es,sv,th,tr,ro;threadSleepTime=5;plugins=;menus=;repositories=;desktops=admin;viewers=default;servers=cm,od,p8,cmis;key=871bf66c911f811fd48a6cc97aea40a4;objectExpiration=10;desktop=default')
DB20000I  The SQL command completed successfully.

INSERT INTO ECM_SC.CONFIGURATION VALUES ('settings.navigator.default', 'mobileAccess=true;logging.level=2;logging.excludes=com.ibm.ecm.configuration;iconStatus=docHold,docNotes,docMinorVersions,docDeclaredRecord,docBookmarks,docCheckedOut,workItemSuspended,workItemDeadlineImportance,workItemDeadlineReminderSent,workItemLocked,workItemCheckedOut;adminUsers=svc-fn1d01')
DB20000I  The SQL command completed successfully.

INSERT INTO ECM_SC.CONFIGURATION VALUES ('desktop.navigator.admin', 'authenticationType=1;workflowNotification=false;fileIntoFolder=false;showSecurity=false;viewer=default;theme=;name=Admin Desktop;isDefault=Yes;menuPrefix=Default;applicationName=IBM Content Navigator;configInfo=;layout=ecm.widget.layout.NavigatorMainLayout;defaultFeature=ecmClientAdmin;actionHandler=ecm.widget.layout.CommonActionsHandler;servers=cm,od,ci,p8,cmis;repositories=')
DB20000I  The SQL command completed successfully.

jueves, 9 de abril de 2015

EXAMPLE OF RESPONSE FILE FOR SILENT INSTALLATION OF DB2 10.1


PROD=ENTERPRISE_SERVER_EDITION
LIC_AGREEMENT=ACCEPT
FILE=C:\Program Files\IBM\SQLLIB\
INSTALL_TYPE=TYPICAL

LANG=EN
LANG=ES

DAS_CONTACT_LIST=LOCAL

INSTANCE=DB2
DB2.NAME=DB2
DEFAULT_INSTANCE=DB2
DB2.SVCENAME=db2c_DB2
DB2.DB2COMM=TCPIP
DB2_OLEDB_GUID={A9AB88BA-61B6-412C-A625-14239A5DF79E}
DB2_OLEDB_ADVANCED_PAGE_GUID={416DB77A-7BF5-47E0-9033-193EEBA5BB60}
DB2_OLEDB_CONNECTION_PAGE_GUID={0CAA4B82-0BF7-4CDB-888A-CC680D7390F6}
DB2_OLEDB_ENUMERATOR_GUID={E6F33DFE-EEA3-4122-9CF4-3DC266025EF7}
DB2_OLEDB_ERROR_LOOKUP_GUID={7ACEBB7B-E4A2-4836-8507-8909E62D04B3}
DB2.PORT_NUMBER=50000
DB2.AUTOSTART=YES
DB2.USERNAME=db2admin
DB2.PASSWORD=446539629627478989612278444969555334095341267432405270466619657544477754003202585496513676129381949244724646993404661508352044473721568846422292646376305576432682768454565660274816499530475665642907235944454272289258587322839789395483136913374379890776447475483049404506674744754423240595239409573893865322735562388604265375055256386746431224681952333122032365802998170500146347964313840124656633720524855344553483523444533605970794829648180745457119951423235933867475724593376524642863354969403609643788583440535344645272065137832574042781462376926596496156648208456676845565882225674244363673470773412139664324352336792790825269439423779688751043819350652845479653496345622553745639936680438680677365244346253550649741321417676835634733415617021101423528468247952262365704740539333811278104435546856484194779770240776163554480545014267635537697644052765597310867522272553560923409782860633267226350920965195684463226963043732599947693284473271623442737676127100077464262841529402353956612070264566425165325296409990254319206905466146704676406348064797593145288169352463228265331953456566456301065429657496667024384347634820892842748341021907763949652556631941431135494463859050526851487799904094765654424830004145532223492323425144647407041393930774637159944386351222641765474266045540369072324853099590462037030052546335213585927865670758929675849725631532609162271000242170932595579506065341743596443723943792456313634507524297924105955635413546429743648862627308624548947291270575724485063306856628373357481446360966259064293733
ENCRYPTED=DB2.PASSWORD
DAS_USERNAME=db2admin
DAS_PASSWORD=193124105134648915115346816237757567558514808147524768472397483127454745132464944920352494137584415345426047597944415847627396635452849162758674662385767528729497706423222003561779358765630645432385916456936253766231739651229357274516222547956732120857747580156933348343587186539546329334646235888947332546389563482225221651665052273176138055775478906686031038974523049464255286145064582533934544914463354959455502402140375234117443227724262092551666420427960155064211768995678478579975561252933000713676686164446479649364677566905844242868969544475756765389228636549214415184938748621333934322255766403907735773160626424456062105564691030555063095606325799385551496832434719775292153266930980426069990643151236554720925504947668630391451251155759785684832463439759454255522453247677685745635581430528764561340333574150182554427590145162657643774418155463836563353804656387861504135400847638444602624578955567759235260919359545759445301591973656427634366812849696738789005921046539834448645147445681723949184467488628341274477222673426305829171494469862444244551343023597476556584935674837782995887334377522273632747308248875460746391468477854956065535238024927272317744665694569921514747134087468740494673305429526295249668285910046387535813270754581026733087434455535927053057480726445262662641428464986487151644572676472146834519582003593369811035471743791642695165451406731349307687686712030711365914676956285338627015820664345263326174776979924191620344983102305536555445683054381664224736060867173522030322659189567094751549264
ENCRYPTED=DAS_PASSWORD
CREATE_DAS=YES
DB2_EXTSECURITY=YES
DB2_USERSGROUP_NAME=DB2USERS
DB2_ADMINGROUP_NAME=DB2ADMNS
RSP_FILE_NAME=C:\Users\Roberto\Documents\PROD_ESE.rsp
DB2_COPY_NAME=DB2COPY1
DEFAULT_COPY=YES

THE APPROPIATTE SERVICE PACK SOLVES THE ISSUE O THE WINDOWS 2012 AND DB2

Considerations before installing DB2 for Windows on 

or prior to 10.5 Fix Pack 3, 10.1 Fix Pack 3 and 9.7 Fix 

Pack 9 on Windows 8.1 and Windows 2012 R2

Technote (troubleshooting)


Problem(Abstract)

While installing DB2 for Windows on or prior to 10.5 Fix Pack 3, 10.1 Fix Pack 3 and 9.7 Fix Pack 9 on 
Windows 8.1 and Windows 2012 R2, you might receive GUI related errors, errors related to shortcuts
 created during the installation, and errors pertaining to the db2prereqcheck tool.

Symptom

One of the following three error symptoms might be encountered during installation on Windows 8.1 & 
Windows 2012 R2.
1. GUI mode of Domain installation might fail with the "Windows installer has stopped working" 
error on "Select the installation type" Dialog.


2. GUI mode of Fix Pack update installation may fail with the following error:


3. Shortcuts created under All Apps for the default DB2 copy do not start on invocation immediately
 after installation.

4. With DB2 V10.1, the db2prereqcheck tool reports Windows 8.1 and Windows 2012 R2 as
 not supported platform:

Checking DB2 prerequisites for DB2 database version "10.1.0.3" on operating
 system "Windows"
OS is Windows "Server"
ERROR: Requirement not matched.
Requirement not matched for DB2 database "Server" . Version: "10.1.0.3".
Summary of prerequisites that are not met on the current system:
Requirement not matched for DB2 database "Server" . Version: "10.1.0.3".

Environment

Windows 8.1, Windows 2012 R2

Resolving the problem

For the currently available fix packs, choose the silent installation method using response 
files in the following scenarios as we do not have fully enabled GUI installs yet. This helps
 avoid the first two errors listed in the symptom section:
1. Domain installation
2. Fix Pack update installation
Further instructions on performing a silent installation using response files can be found in the
 "Related information" section below.

Also, if the shortcuts created under the All Apps directory for the DB2 copy do not start on
 invocation after the installation of DB2 for Windows either through the GUI or silent installation, 
log off and log back on again.

The db2prereqcheck tool reports Windows 8.1 and Windows 2012 R2 as not supported platforms 
for DB2. However, installation can be performed on these platforms using the resolutions provided
 in this document.

These possible issues are resolved in 10.5 Fix Pack 4.
In 10.1 Fix Pack 4, the first two and the fourth issue are addressed. The third issue
 will be addressed in the future fix pack of 10.1.

Related information

miércoles, 1 de abril de 2015

DB2 configuration


------------------------------ Mandatos entrados ------------------------------
connect to IWBPM ;
------------------------------------------------------------------------------
connect to IWBPM

   Información de la conexión con la base de datos

 Servidor bases datos   = DB2/NT64 9.7.5
 ID autorización SQL    = SYSTEM
 Alias base datos local = IWBPM


Una conexión de JDBC con el destino ha resultado satisfactoria.
------------------------------ Mandatos entrados ------------------------------
CONNECT TO IWBPM;
CREATE  LARGE  TABLESPACE CEDATA_TS PAGESIZE 32 K  MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.14 BUFFERPOOL  IBMDEFAULTBP ;
CONNECT RESET;
------------------------------------------------------------------------------
CONNECT TO IWBPM

   Información de la conexión con la base de datos

 Servidor bases datos   = DB2/NT64 9.7.5
 ID autorización SQL    = SYSTEM
 Alias base datos local = IWBPM


CREATE  LARGE  TABLESPACE CEDATA_TS PAGESIZE 32 K  MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 16 OVERHEAD 10.5 PREFETCHSIZE 16 TRANSFERRATE 0.14 BUFFERPOOL  IBMDEFAULTBP
DB20000I  El mandato SQL ha finalizado satisfactoriamente.

CONNECT RESET

DB20000I  El mandato SQL ha finalizado satisfactoriamente.

Extended Windows Security feature

SQL5005C system error pop-up window when logging into a Windows system due to the logon userid not having permission to run db2systray

Error SQL5005C on Windows Vista, Windows 7

 and Windows 2008

Technote (troubleshooting)


Problem(Abstract)

When I try to run any DB2 command in Windows Vista, Windows 7 and Windows 2008 I get the following error:

C:\Program Files\IBM\SQLLIB\BIN>db2 list db directory
SQL5005C System Error.

Resolving the problem

The cause of this error is because you may not have picked "Run as Administrator" when installing DB2.

If you right click on any icon you will have an option to "Run as Administrator":

You can either do this every time you want to open a DB2 Command Window or 

you can uninstall and reinstall DB2. Before installing DB2 right click on db2setup.exe

 and select "Run as Administrator", see screen shot above.Technote (troubleshooting)


Problem(Abstract)

SQL5005C system error pop-up window when logging into a Windows system due to the logon userid 
not having permission to run db2systray

Symptom

When logging into a Windows system with a userid that is not part of either the DB2ADMNS or
 DB2USERS Extended Windows Security groups, a pop-up that displays an error "SQL5005C system error" will be displayed on the screen if the db2systray is enabled.

Cause

The error is caused by db2systray.exe trying to launch, but the userid that is logging into the system 
does not have the appropriate permission to run db2systray.exe

Resolving the problem

To avoid this error message, please take one of the following steps:
  • This error will not be displayed if the Extended Windows Security feature is not enabled
  • . When installing DB2 for the first time, you may disable the Extended Windows Security 
  • feature in the install wizard when installing DB2 and the error will not occur in this configuration.
  • If Extended Windows Security is enabled, this error message will not be displayed if the
  •  userid that is logging into the system belongs to the DB2USERS or DB2ADMNS group.
  • If Extended Windows Security is enabled, but there are userids on the box that you
  •  do not wish to add to either the DB2USERS or DB2ADMNS group, the error can be avoided by disabling the db2systray feature. To do this, log in as a local administrator and run "db2systray -clean" from a DB2 Command Window with administrative privileges.

Related information

zen consultora

Blogger Widgets