Documente Academic
Documente Profesional
Documente Cultură
Search
Skip to content
Home
FAQ
Books
Usage Terms
Uncategorized
Uncategorized
For creation of Content store, the database must support Unicode Character set. Ensure that
Oracle is installed with a Unicode Character set.
To check whether the installed Oracle database supports Unicode Character set, type the
following SQL Select * from NLS_DATABASE_PARAMETERS;
Create a user and grant Create & Drop privileges for the content store to the user account
Ensure the user account is granted CONNECT and RESOURCE roles.
IIS
Internet Information Services should be installed and running.
Installation
The steps guide the user to install Cognos ReportNet on a single computer. This installation takes
the default path of Cognos. The components that gets installed are
1. ReportNet Server
2. Content Manager
3. Dispatcher
Note: Components can be installed in different systems. For configuration of such installations
refer Cognos Documentation.
Post Installation Configuration
The following points must be taken care of before accessing the Cognos ReportNet tools and
must follow the same order.
1. Set-up of JDBC Client for Cognos Applications to Content store.
2. Set-up database connection properties.
3. Configure Web Server
Note: This document will focus on Oracle Database and Internet Information Services (IIS) Web
Server only.
Set-up of JDBC Client for Cognos Applications to access Content store
Cognos Applications interact with Content store only through JDBC Client. Hence ensure that
proprietary JDBC client of Oracle is made available in Cognos default libraries path. Follow the
below steps to ensure the same.
1. Rename the classes12.zip file to classes12.jar file (Note: Ensure that the file extension option
in explorer window is enabled)
2. Copy the classes12.zip file from Oracle home directory and paste the same under Cognos
Default location.
Set-up of Database Connection properties
ReportNet. Hence in order for Cognos applications to work, Cognos ReportNet needs to be
configured with Content Store. The following steps guide you to configure content store using
Cognos Configuration tool.
For all installations, the database server information must be provided to ensure that ReportNet
can connect to the database to use the content store.
Note: The following steps guide to configure only for Oracle Database. For other databases
please refer Cognos manual.
1. Open Cognos Configuration from Start -> Cognos ReportNet -> Cognos Configuration
2. Right Click on Content Store under Data Access-> Content Manager and Delete.
3. Right Click, Content manager, and then click New Resource, Database. The following
window shows the same.
5. Enter the Database Server name, Port Number and Service Name.
8. Stop
the services.
9. Start
the services
Configure Web Server (IIS) The following virtual directory needs to be created Cognos
Applications to run over Web.
a) Alias Name: crn
Path: crn_locationwebcontent
Permission: Read
b) Alias Name: crn/cgi-bin
Path: crn_locationcgi-bin
Permission: Execute
c) Alias Name: crn/help
Permission: Read
Note: The names of the virtual directories presented in this document are default. The names can
be changed but cgi-bin and help names CANNOT be changed and must remain the same.
Test Installation and Configuration
Test the installation by starting the services using Cognos Configuration. Once started open
browser and type the following URL http://hostname/crn
The following Cognos Portal on the browser will ensure that your installation and configuration
is correct.
log (crnconfiguration)
Potential Problems & Solutions
trying to initialize.
Problem 1: The database does not support Unicode Character Set
Solution 1:
1. Check whether the database installed supports UTF-8 Encoding. If not migrate to UTF8 from
the current Character set.
2. Re-install database with UTF 8 Encoding
Problem 2: The database connection parameters might be wrong
Solution 2: Ensure the database parameters furnished in Content manager is correct. Test the
same through the Client of RDBMS vendor.
Cognos BI is not available
Problem: The ReportNet service is stopped.
Solution: The ReportNet services should be started. Go to Cognos configuration and start the
services.
Problem: Insufficient Privileges
Solution: Ensure that the User to connect to Content Store has the Create and Drop Privileges
and Connect and Resource Roles .
Solution: In Cognos Connection in the Content Store node, ensure the Service Name Property
(the SID) is not fully qualified.
The JDBC Driver uses the SID, not the fully qualified name.
Problem: DPR-CMI-4007 An request to perform an active content manager election failed
Solution: Delete the existing content store connection and recreate the same.
Problem: Unable to log into Cognos Connection.
DPR-ERR-2058 The dispatcher cannot service the request at this time. The dispatcher is still
initializing
Solution: In this case, the problem was that the Content Manager host and port number were
accidentally modified and the port number was incorrect.
Problem: Tables are locked.
CM-SYS-5007 Content Manager build 1.1.162.0 failed to start! Review the Content Manager
log files and then contact your system administrator or customer support. CM-CFG-5063 A
Content Manager configuration error was detected while connecting to the content store.
Solution: The tables are locked due to previous improper configuration. Solution is to drop the
tables manually, save the configuration in Content manager and restart the services.
Solution: Read the below below script and make fresh schema using it.
Uncategorized
Uncategorized
Uncategorized
2) Find the origional PVID. This might be seen with lspv importvg, or
varyonvg. Our example origional PVID is 0012a3e42bc908f3
# lqueryvg -Atp /dev/hdisk9
...
Physical: 0012a3e42bc908f3 2 0
00ffffffc9cc5f99 1 0
...
3) Verify that the disk sees an invalid PVID. The first 2 data fields
of offset 80 contain the PVID.
# lquerypv -h /dev/hdisk9 80 10
00000080 00001155 583CD4B0 00000000 00000000 |...UX<..........|
^^^^^^PVID^^^^^^^
4) Translate the ORIGIONAL PVID into the octal version. Take every 2
digits of the hex PVID and translate it to octal. This can be done
by hand, calculator, script, or web page.
00012a3e42bc908f3 -> 00 12 a3 e4 2b c9 08 f3
Octal version -> 000 022 243 344 053 311 010 363
5) Write the binary version of the PVID to a file by using the octal
values. Each octal char is lead with a backslash-Zero . Do
not use spaces or any other characters except for the final c to
keep from issuing a hard return.
# echo "000022243344053311010363c" >/tmp/oldpvid
6) Verify that the binary pvid was written correctly. The origional
hex PVID should be seen AND the final address should be 0000010
If EITHER of these is incorrect, try again, make sure there are no
spaces in the echo and the echo ends with a c.
# od -x /tmp/oldpvid
0000000 0012 a3e4 2bc9 08f3
0000010
7) Restore the PVID to the disk. You sould see 8 records in and out.
If there are more or less, restore the origional 4K block by using
the recovery method in step 1.
# cat /tmp/oldpvid | dd of=/dev/hdisk9 bs=1 seek=128
8+0 records in.
8+0 records out.
Solaris
# vi /kernel/drv/scsi_vhci.conf
b. Verify that the load-balance and auto-failback parameters are set to the following values(the
default setting may vary depending on the patch level / OS version):
load-balance="none";
auto-failback="disable";
NOTE:
Enter six spaces after HP and two spaces after COMPAQ.
3. For Solaris 10 (patch 118833-24 for SPARC, patch 118855-19 for x86), the scsi_vhci driver is
capable of detecting Asymmetric Logical Unit Access (ALUA) compliant devices advertised in
the Target Port Group Support (TPGS) field. The EVA 4000/6000/8000 and the EVA 3000/5000
V4 are ALUA compliant arrays. Add the following lines to cover all HP arrays:
device-type-scsi-options-list =
"HP OPEN", "symmetric-option";
symmetric-option = 0x1000000;NOTE:
b. For Solaris 10 (SPARC)run the stmsboot command and confirm the reboot:
# stmsboot e
c. For Solaris 10 (x86)reboot the system to load the new definition if you are configuring for
XP. Configuring for EVA does not require a reboot since definition has already been configured.
Original post blogged on b2evolution.
Uncategorized
# chtz IST-5:30
Restart xntpd
# startsrc -s xntpd
Original post blogged on b2evolution.
Uncategorized
Note : Always use single initiator Zone which typically include one storage and one host wwpn.
Original post blogged on b2evolution.
Uncategorized