Mengatasi Error Installasi Database PostgreSQL di Window 7

Pernah mengalami error saat Installasi database PostgreSQL di Window 7 ? dengan pesan error : The 'Secondary Logon' is not running seperti gambar berikut :



Solusinya sebagai berikut :
1. Buka Control Panel
2. Pilih ( klik 2x ) Administrative Tools
3. Pilih ( klik 2x ) Services
4. Pilih 'Secondary Logon'
5. Pilih StartUp Type menjadi Automatic
6. Klik tombol Start 

Selamat mencoba...

Cara Membuka File Help (*.hlp) di Window 7

File Dokumen Help atau file berekstention *.hlp tidak dapat dibuka pada OS Window 7.
Agar  File Help (*.hlp) tersebut dapat dibuka pada Window 7 maka Cara Membuka File Help (*.hlp) di Window 7 tersebut yaitu dengan mendownload update KB917607 dengan langah-langkah berikut:

Silahkan Download Update dari Microsoft KB917607 di bawah ini :

1. For 32-bit (x86) (687,31 KB) untuk kapasitas netbook

2. For 64-bit (x64) (701,33 KB) untuk kapasitas laptop dan komputer

Setelah Download maka akan terbuka proses instalasi update dari Microsoft KB917607,

Silahkan Klik OK, 

Kemudian pilih I Accept menyatan setuju untuk di instal dan proses berlanjut lainnya, hingga proses instalasi selesai ok, 

Close.

Selamat mencoba... :-)

Backup Database Sybase

Description

Makes a backup copy of the entire database, including the transaction log, in a form that can be read in with load database. Dumps and loads are performed through Backup Server.
The target platform of a load database operation need not be the same platform as the source platform where the dump database operation occurred. dump database and load database are performed from either a big endian platform to a little endian platform, or from a little endian platform to a big endian platform.

Syntax

dump database database_name
 to [compress::[compression_level::]]stripe_device
  [at backup_server_name]
  [density = density_value, 
  blocksize = number_bytes, 
  capacity = number_kilobytes, 
  dumpvolume = volume_name, 
  file = file_name] 
  with verify[ = header | full]
 [stripe on [compress::[compression_level::]]stripe_device
  [at backup_server_name]
  [density = density_value, 
  blocksize = number_bytes,
  capacity = number_kilobytes, 
  dumpvolume = volume_name,
  file = file_name]] 
 [[stripe on [compress::[compression_level::]]stripe_device
  [at backup_server_name]
  [density = density_value, 
  blocksize = number_bytes,
  capacity = number_kilobytes, 
  dumpvolume = volume_name,
  file = file_name]]...]
 [with { 
  density = density_value, 
  blocksize = number_bytes,
  capacity = number_kilobytes, 
  compression = compress_level
  dumpvolume = volume_name,
  file = file_name,
  [dismount | nodismount],
  [nounload | unload],
  passwd = password,
  retaindays = number_days,
  [noinit | init],
  notify = {client | operator_console}
  } ] 

Parameters

database_name

is the name of the database from which you are copying data. The database name can be specified as a literal, a local variable, or a stored procedure parameter.

compress::compression_level

is a number between 0 and 9, with 0 indicating no compression, and 9 providing the highest level of compression. If you do not specify compression_level, the default is 1. See Chapter 28, “Backing Up and Restoring User Databases” in the System Administration Guide for more information about the compress option.

Sybase recommends the native "compression = compress_level" option as preferred over the older "compress::compression_level" option. The native option allows compression of both local and remote dumps, and the dumps that it creates will describe their own compression level during a load. The older option is retained for compatibility with older applications.

to stripe_device

is the device to which to copy the data. See “Specifying dump devices” in this section for information about what form to use when specifying a dump device.

at backup_server_name

is the name of the Backup Server. Do not specify this parameter when dumping to the default Backup Server. Specify this parameter only when dumping over the network to a remote Backup Server. You can specify as many as 32 remote Backup Servers with this option. When dumping across the network, specify the network name of a remote Backup Server running on the machine to which the dump device is attached. For platforms that use interfaces files, the backup_server_name must appear in the interfaces file.

density = density_value

overrides the default density for a tape device. Valid densities are 800, 1600, 6250, 6666, 10000, and 38000. Not all values are valid for every tape drive; use the correct density for your tape drive.

blocksize = number_bytes

overrides the default block size for a dump device. The block size must be at least one database page (2048 bytes for most systems) and must be an exact multiple of the database page size. For optimal performance, specify the blocksize as a power of 2, for example, 65536, 131072, or 262144.

capacity = number_kilobytes

is the maximum amount of data that the device can write to a single tape volume. The capacity must be at least five database pages and should be less than the recommended capacity for your device.
A general rule for calculating capacity is to use 70 percent of the manufacturer’s maximum capacity for the device, allowing 30 percent for overhead such as record gaps and tape marks. The maximum capacity is the capacity of the device on the drive, not the drive itself. This rule works in most cases, but may not work in all cases due to differences in overhead across vendors and across devices.
On UNIX platforms that cannot reliably detect the end-of-tape marker, indicate how many kilobytes can be dumped to the tape. You must supply a capacity for dump devices specified as a physical path name. If a dump device is specified as a logical device name, the Backup Server uses the size parameter stored in the sysdevices system table unless you specify a capacity.

compression = compress_level

is a number between 1 and 9, with 9 providing the highest level of compression. There is no default compression level; if you do not specify compression = compress_level, Adaptive Server does not compress the dump.

Sybase recommends the native "compression = compress_level" option as preferred over the older "compress::compression_level" option. The native option allows compression of both local and remote dumps, and the dumps that it creates will describe their own compression level during a load. The older option is retained for compatibility with older applications.

dumpvolume = volume_name

establishes the name that is assigned to the volume. The maximum length of volume_name is 6 characters. Backup Server writes the volume_name in the ANSI tape label when overwriting an existing dump, dumping to a new tape, or dumping to a tape whose contents are not recognizable. The load database command checks the label and generates an error message if the wrong volume is loaded.

WARNING!  Label each tape volume as you create it so that the operator can load the correct tape.

with verify[ = header | full]

allows the backupserver to perform a minimal header or structural row check on the data pages as they are being copied to the archives. There are no structural checks done at this time to gam, oam, allocation pages, indexes, text, or log pages. The only other check is done on pages where the page number matches to the page header.

stripe on stripe_device

is an additional dump device. You can use as many as 32 devices, including the device named in the to stripe_device clause. The Backup Server splits the database into approximately equal portions, and sends each portion to a different device. Dumps are made concurrently on all devices, reducing the time required to make a dump and requiring fewer volume changes during the dump. See “Specifying dump devices” for information about how to specify a dump device.

dismount | nodismount

on platforms that support logical dismount, determines whether tapes remain mounted. By default, all tapes used for a dump are dismounted when the dump completes. Use nodismount to keep tapes available for additional dumps or loads.

nounload | unload

determines whether tapes rewind after the dump completes. By default, tapes do not rewind, allowing you to make additional dumps to the same tape volume. Specify unload for the last dump file to be added to a multidump volume. This rewinds and unloads the tape when the dump completes.

passwd = password

is the password you provide to protect the dump file from unauthorized users. The password must be between 6 and 30 characters long.

retaindays = number_days

on UNIX systems – when dumping to disk, specifies the number of days that Backup Server protects you from overwriting the dump. If you try to overwrite the dump before it expires, Backup Server requests confirmation before overwriting the unexpired volume.

This option is meaningful only when dumping to a disk. It is not meaningful for tape dumps.

The number_days must be a positive integer or 0, for dumps that you can overwrite immediately. If you do not specify a retaindays value, Backup Server uses the tape retention in days value set by sp_configure.

noinit | init

determines whether to append the dump to existing dump files or reinitialize (overwrite) the tape volume. By default, Adaptive Server appends dumps following the last end-of-tape mark, allowing you to dump additional databases to the same volume. New dumps can be appended only to the last volume of a multivolume dump. Use init for the first database you dump to a tape to overwrite its contents.
Use init when you want Backup Server to store or update tape device characteristics in the tape configuration file. For more information, see the System Administration Guide.

file = file_name

is the name of the dump file. The name cannot exceed 17 characters and must conform to operating system conventions for file names. For more information, see “Dump files”.

notify = {client | operator_console}

overrides the default message destination.
On operating systems that offer an operator terminal feature, volume change messages are always sent to the operator terminal on the machine on which Backup Server is running. Use client to route other Backup Server messages to the terminal session that initiated the dump database.
On operating systems that do not offer an operator terminal feature, such as UNIX, messages are sent to the client that initiated the dump database. Use operator_console to route messages to the terminal on which Backup Server is running.

Examples

Example 1

Dumps the database pubs2 to a tape device. If the tape has an ANSI tape label, this command appends this dump to the files already on the tape, since the init option is not specified:

dump database pubs2 
    to "/dev/nrmt0"

Example 2

For UNIX – dumps the pubs2 database, using the REMOTE_BKP_SERVER Backup Server. The command names three dump devices, so the Backup Server dumps approximately one-third of the database to each device. This command appends the dump to existing files on the tapes. On UNIX systems, the retaindays option specifies that the tapes cannot be overwritten for 14 days:

dump database pubs2
    to "/dev/rmt4" at REMOTE_BKP_SERVER
    stripe on "/dev/nrmt5" at REMOTE_BKP_SERVER
    stripe on "/dev/nrmt0" at REMOTE_BKP_SERVER
with retaindays = 14

Example 3

The init option initializes the tape volume, overwriting any existing files:

dump database pubs2
    to "/dev/nrmt0"
    with init

Example 4

Rewinds the dump volumes upon completion of the dump:

dump database pubs2
    to "/dev/nrmt0"
    with unload

Example 5

For UNIX – the notify clause sends Backup Server messages requesting volume changes to the client which initiated the dump request, rather than sending them to the default location, the console of the Backup Server machine:

dump database pubs2
    to "/dev/nrmt0"
    with notify = client

Example 6

Creates a compressed dump of the pubs2 database into a local file called dmp090100.dmp using a compression level of 4:

dump database pubs2 to 
    "compress::4::/opt/bin/Sybase/dumps/dmp090100.dmp"

Alternatively, you can create a compressed dump of the pubs2 database into a local file called dmp090100.dmp using a compression level of 4 using compression = compression_level syntax

dump database pubs2 to "/opt/bin/Sybase/dumps/dmp090100.dmp" 
    with compression = 4

Example 7

Dumps the pubs2 database to the remote machine called “remotemachine” and uses a compression level of 4:

dump database pubs2 to "/Syb_backup/mydb.db" at remotemachine 
    with compression = "4"

src : http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.commands/html/commands/commands68.htm

Restore or load database sybase

Description

Loads a backup copy of a user database, including its transaction log, that was created with dump database.
The target platform of a load database operation need not be the same platform as the source platform where the dump database operation occurred. dump database and load database are performed from either a big endian platform to a little endian platform, or from a little endian platform to a big endian platform.

Syntax

To make a routine database load:

load database database_name 
 from [compression=]stripe_device 
  [at backup_server_name ]
  [density = density_value, 
  blocksize = number_bytes, 
  dumpvolume = volume_name, 
  file = file_name] 
  with verify only [ = header | full]
 [stripe on [compression=]stripe_device 
  [at backup_server_name ]
  [density = density_value, 
  blocksize = number_bytes,
  dumpvolume = volume_name, 
  file = file_name]
 [[stripe on [compression=]stripe_device 
  [at backup_server_name ]
  [density = density_value, 
  blocksize = number_bytes, 
  dumpvolume = volume_name, 
  file = file_name]]...]
 [with {
  density = density_value, 
  blocksize = number_bytes, 
  compression, 
  dumpvolume = volume_name, 
  file = file_name, 
  [dismount | nodismount],
  [nounload | unload],
  passwd = password, 
  notify = {client | operator_console}
  }]]

To return header or file information without loading the backup:

load database database_name 
 from [compress::]stripe_device 
  [at backup_server_name ] 
  [density = density_value, 
  blocksize = number_bytes, 
  dumpvolume = volume_name, 
  file = file_name]
 [stripe on [compress::]stripe_device
  [at backup_server_name ] 
  [density = density_value, 
  blocksize = number_bytes, 
  dumpvolume = volume_name, 
  file = file_name] 
 [[stripe on [compress::]stripe_device 
  [at backup_server_name ] 
  [density = density_value, 
  blocksize = number_bytes, 
  dumpvolume = volume_name, 
  file = file_name]]...] 
 [with {
  density = density_value,, 
  blocksize = number_bytes, 
  compression, 
  dumpvolume = volume_name, 
  file = file_name, 
  [dismount | nodismount],
  [nounload | unload],
  passwd = password, 
  listonly [= full],
  headeronly, 
  notify = {client | operator_console}
  }]]

Parameters

database_name

is the name of the database to receive the backup copy. It can be either a database created with the for load option, or an existing database. Loading dumped data to an existing database overwrites all existing data. The receiving database must be at least as large as the dumped database. The database name can be specified as a literal, a local variable, or a stored procedure parameter.

compress::

invokes the decompression of the archived database. For more information about the compress option, see Chapter 27, “Backing Up and Restoring User Databases” in the System Administration Guide.

Sybase recommends the native "compression = compress_level" option as preferred over the older "compress::compression_level" option. If you use the native option for dump database, you do not need to use "compress::compression_level" when loading your database.

from stripe_device

is the device from which data is being loaded. See “Specifying dump devices” for information about what form to use when specifying a dump device. For a list of supported dump devices, see the Adaptive Server installation and configuration guides.

at backup_server_name

is the name of a remote Backup Server running on the machine to which the dump device is attached. For platforms that use interfaces files, the backup_server_name must appear in the interfaces file.

density = density_value

is ignored. For more information, see the dump database command.

blocksize = number_bytes

overrides the default block size for a dump device. If you specify a block size on UNIX systems, it should be identical to that used to make the dump. For more information, see the dump database command.

dumpvolume = volume_name

is the volume name field of the ANSI tape label. load database checks this label when the tape is opened and generates an error message if the wrong volume is loaded.

When using load database, the dumpvolume option does not provide an error message if an incorrect file name is given for the file=filename option. The backup server searches the entire tape looking for that file, regardless of an incorrect tape mounted.

file = file_name

is the name of a particular database dump on the tape volume. If you did not record the dump file names when you made the dump, use listonly to display information about all dump files.

stripe on stripe_device

is an additional dump device. You can use up to 32 devices, including the device named in the to stripe_device clause. The Backup Server loads data from all devices concurrently, reducing the time and the number of volume changes required. See “Specifying dump devices” for more information.

compression

indicates that the database you are loading was compressed to a file on a remote server. You do not need to specify the compression level for load database.

Sybase recommends the native "compression = compress_level" option as preferred over the older "compress::compression_level" option. If you use the native option for dump database, you do not need to use "compress::compression_level" when loading your database.

dismount | nodismount

on platforms that support logical dismount – determines whether tapes remain mounted. By default, all tapes used for a load are dismounted when the load completes. Use nodismount to keep tapes available for additional loads or dumps.

nounload | unload

determines whether tapes rewind after the load completes. By default, tapes do not rewind, allowing you to make additional loads from the same tape volume. Specify unload for the last dump file to be loaded from a multidump volume. This rewinds and unloads the tape when the load completes.

passwd = password

is the password you provided to protect the dump file from unauthorized users. The password must be between 6 and 30 characters long.

listonly [ = full]

displays information about all dump files on a tape volume, but does not load the database. listonly identifies the database and device, the date and time the dump was made, and the date and time it can be overwritten. listonly = full provides additional details about the dump. Both reports are sorted by ANSI tape label.
After listing the files on a volume, the Backup Server sends a volume change request. The operator can either mount another tape volume or terminate the list operation for all dump devices.
Due to current implementation, the listonly option overrides the headeronly option.

WARNING! Do not use load database with listonly on 1/4-inch cartridge tape.

with verify only [ = header | full]

The backupserver performs a minimal header or structural row check on the data pages as they are being copied to the archives. There are no structural checks done at this time to gam, oam, allocation pages, indexes, text, or log pages. The only other check is done on pages where the page number matches to the page header.

headeronly

displays header information for a single dump file, but does not load the database. headeronly displays information about the first file on the tape unless you use the file = file_name option to specify another file name. The dump header indicates:

• Type of dump (database or transaction log)
  
• Database ID
  
• File name
  
• Date the dump was made
  
• Character set
  
• Sort order
  
• Page count
  
• Next object ID
  

notify = {client | operator_console}

overrides the default message destination.

• On operating systems that offer an operator terminal feature, volume change messages are always sent to the operator terminal on the machine on which the Backup Server is running. Use client to route other Backup Server messages to the terminal session that initiated the dump database.
  
• On operating systems (such as UNIX) that do not offer an operator terminal feature, messages are sent to the client that initiated the dump database. Use operator_console to route messages to the terminal on which the Backup Server is running.
  

Examples

Example 1

Reloads the database pubs2 from a tape device:

load database pubs2 
    from "/dev/nrmt0"

Example 2

Loads the pubs2 database, using the Backup Server REMOTE_BKP_SERVER. This command names three devices:

load database pubs2
        from "/dev/nrmt4" at REMOTE_BKP_SERVER
    stripe on "/dev/nrmt5" at REMOTE_BKP_SERVER
    stripe on "/dev/nrmt0" at REMOTE_BKP_SERVER

Example 3

Loads the pubs2 database from a compressed dump file called dmp090100.dmp located at /opt/bin/Sybase/dumps:

load database pubs2 from 
    "compress::/opt/bin/Sybase/dumps/dmp090100.dmp"

source : http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.ase_15.0.commands/html/commands/commands68.htm 

Online database sybase

Untuk mengaktifkan database sybase yang baru direstore kita dapat melakukannya dengan cara menjalankan fungsi online database. Adapun penjelasan mengenai fungsi online database sybase dapat dilihat pada penjelasan berikut ini :

Description

Marks a database available for public use after a normal load sequence; if needed, upgrades a loaded database to the current version of Adaptive Server; brings a database online after loading a transaction log dumped with the for standby_access option.

Syntax

online database database_name [for standby_access]

Parameters

database_name

specifies the name of the database to be brought online.

for standby_access

brings the database online on the assumption that the database contains no open transactions.

Examples

Example 1

Makes the pubs2 database available for public use after a load sequence completes:

online database pubs2

Example 2

Brings the database inventory_db online. Used after loading inventory_db with a transaction-log dump obtained through dump tran...with standby_access:

online database inventory_db for standby_access

Usage

• online database brings a database online for general use after a normal database or transaction log load sequence.
  
• When load database is issued, the database’s status is set to “offline.” The offline status is set in the sysdatabases system table and remains set until online database completes.
  
• Do not issue online database until all transaction logs are loaded. The command sequence is:
  
  • load database
    
  • load transaction (there may be more than one load transaction)
    
  • online database
    
• If you execute online database against a currently online database, no processing occurs and no error messages are generated.
  
• You can only use online database...for standby_access with a transaction log that was dumped using dump transaction...with standby_access. If you use online database...for standby_access after loading a transaction log that was dumped without using dump transaction...with standby access, online database generates an error message and fails.
  
• You can use sp_helpdb to find out whether a database is currently online, online for standby access, or offline.
  

Upgrading databases

• online database initiates, if needed, the upgrade of a loaded database and transaction log dumps to make the database compatible with the current version of Adaptive Server. After the upgrade completes, the database is made available for public use. If errors occur during processing, the database remains offline.
  
• online database is required only after a database or transaction log load sequence. It is not required for new installations or upgrades. When you upgrade Adaptive Server to a new version, all databases associated with that server are automatically upgraded.
  
• online database only upgrades version 11.9 or later user databases.
  
• After you upgrade a database with online database, dump the newly upgraded database to create a dump that is consistent with the current version of Adaptive Server. You must dump the upgraded database before you can issue a dump transaction command.
  

Get the count of rows selected

long ll_Selected

ll_Selected = &
  long(dw_1.describe("evaluate('sum( if(isselected(), 1, 0) for all)',1)"))

Source : http://www.rgagnon.com/pbdetails/pb-0183.html 

Get Page Number of the Report

Put the datawindow into print preview mode

dw_1.modify &
  ( 'datawindow.print.preview=yes' )

Get the result of the 'PageCount()' expression

ll_PageCount = &
   long ( dw_1.describe &
     ("evaluate('pagecount()'," + string ( dw_1.rowcount() ) + ")"))