510-701 questions are changed today. Download new questions.

killexams.com 510-701 test prep contains a Complete Pool of Questions and Answers and Free PDF confirmed and substantial including references and clarifications (where appropriate). Our objective to rehearse the Sybase IQ Administrator 12.6 Professional PDF Braindumps is not just to finish the 510-701 test at first endeavor however Really Improve Your Knowledge about the 510-701 test course destinations.

Exam Code: 510-701 Practice exam 2022 by Killexams.com team
Sybase IQ Administrator 12.6 Professional
Sybase Administrator guide
Killexams : Sybase Administrator guide - BingNews https://killexams.com/pass4sure/exam-detail/510-701 Search results Killexams : Sybase Administrator guide - BingNews https://killexams.com/pass4sure/exam-detail/510-701 https://killexams.com/exam_list/Sybase Killexams : NetBackup™ Commands Reference Guide

Long Display Format (-L)

If the command line contains -L, the display format is long. It contains a multi-line entry for each backup image. The number of lines for an entry is n+1, where n is the number of fragments for the image. The fields for an entry are listed later. The first line of the entry contains the fields Backup_ID...Expires. Each fragment in the image has a line that contains the fields Copy_Media ID. The report has a two-line header. The first header line lists the field names for line 1 of each entry. The second header line lists the field names for the lines that contain fragment information.

See the bpduplicate command page for more information on the copy number and primary copy.

Fields and meanings for the -L format are as follows:

Line 1

Backup-ID - Unique identifier for the backup that produced this image

Policy - Policy name (may be truncated if long)

Type - Schedule type (FULL, etc.)

RL - Retention level (0.100)

If you run this command on a pre-NetBackup 8.0 media server, the output only displays the retention levels between 0 and 24.

Files - Number of files in the backup

C - Compression (Y or N)

E - Encryption (Y or N)

T - Image type

R - Regular (scheduled or user-directed backup)

P - Pre-imported backup (phase 1 completed)

I - Imported backup

PC - Primary copy, 1 or 2. Designates which copy of the backup NetBackup chooses when it restores.

Image-DTE-Mode - DTE mode of backup image.

Expires - The expiration date of the first copy to expire, which appears in the Expires field of the fragment, which is described later.

Line 2_n+1

Copy - Copy number of this fragment

Frag - Fragment number or IDX for a true-image-restore (TIR) fragment

KB - Size of the fragment, in kilobytes. This value does not include the size of tape headers between backups. A fragment size of 0 is possible for a multiplexed backup.

Type - Media type (Rmed - removable media; Disk otherwise)Density - Density of the removable media that produced the backupFnum - File number; the n-th backup on this removable media Host - Server whose catalog contains this imageDWO - Device Written On; device where the backup was written. The DWO matches the drive index as configured in Media Manager (applies only to removable media).

MPX - Flag that indicates whether this copy is multiplexed: Y or N (applies only when fragment number is 1)

Expires - The expiration date of this copy (applies only when fragment number is 1)

MediaID - Media ID or absolute path where the image is stored

Copy-DTE-Mode - The copy DTE mode is On if DTE was enabled for the data transfer job that created this copy.

Hierarchical-DTE-Mode - The copy hierarchical DTE mode is On if the copy hierarchical DTE mode of the source image was On and DTE was enabled for the data transfer job which created this copy.

Short Display Format (-l)

If the bpconfig command line contains -l or contains no list-format option, the display format is short, which produces a terse listing. This option can be useful for scripts or the programs that rework the listing into a customized report format. The -l display format contains a multi-line entry for each backup image. The number of lines per entry is n+1, where n is the number of fragments for the image. The layout of an entry is a first line that contains information about the image. A second line follows that contains information about each fragment of the image. The attributes appear in the following order (separated by blanks).

Fields for the -l format are as follows:

Field 1 = Client. The name of the image's client.

Field 2 = Version. The NetBackup version of the client.

Field 3 = Image keyword. The keyword for the backup image.

Field 4 = Policy name. The name of the policy that created the image.

Field 5 = Policy type. 0=Standard, 4=Oracle, 8=Sybase, 9=MS-SharePoint

Field 6 = Schedule - Schedule name that is run to create the backup.

Field 7 = Schedule type. 0=Full, 1=Differential incremental, 2=User-directed backup, 3=User-directed archive, 4=Cumulative incremental

Field 8 = Retention level (0-100).

If you run this command on a pre-NetBackup 8.0 media server, the output only displays the retention levels between 0 and 24.

0 = 1 week, 4mm cartridge media

1 = 2 weeks, 8mm cartridge media

2 = 3 weeks, 8mm2 cartridge media

3 = 1 month, 8mm3 cartridge media

4 = 2 months, dlt cartridge media

5 = 3 months, dlt2 cartridge media

6 = 6 months, dlt3 cartridge media

7 = 9 months, dtf cartridge media

8 = 1 year, half-inch cartridge media

9-100 = infinite (except 25 which is expire immediately), half-inch cartridge 2 media

Field 9 = Number of files in the image.

Field 10 = Expiration time of the image in seconds since January 1, 1970. A value of zero (0) denotes an image in progress or failed.

Field 11 = Compression. 0=Use compression, 1=Do not use compression

Field 12 = Encryption.

Field 13 = Hold. 0=Image is not on hold, 1=Image is on hold

Field 14 = DTE mode of backup image. 0 is DTE off and 1 is DTE on


Field 1 = Copy number

Field 2 = Fragment number

Field 3 = Fragment size in KBytes

Field 7 = File number

Field 8 = Media. The media where the image is stored.

Field 9 = The media server for the image.

Field 10 = Block size in KBytes

Field 11 = Offset

Field 12 = The time (in seconds since January 1, 1970) when the fragment was created

Field 13 = The device number where the image was written

Field 16 = Expiration time of the image in seconds since January 1, 1970. A value of zero (0) denotes an image in progress or failed.

Field 17 = Multiplexing. 0=multiplexing not used, 1=multiplexing used

Field 18 = Retention level.

0 = 1 week, 4mm cartridge media

1 = 2 weeks, 8mm cartridge media

2 = 3 weeks, 8mm2 cartridge media

3 = 1 month, 8mm3 cartridge media

4 = 2 months, dlt cartridge media

5 = 3 months, dlt2 cartridge media

6 = 6 months, dlt3 cartridge media

7 = 9 months, dtf cartridge media

8 = 1 year, half-inch cartridge media

9-100 = infinite (except 25 which is expire immediately), half-inch cartridge 2 media

Field 20 = Hold. 0=Fragment not on hold, 1=Fragment on hold

Field 22 = Copy DTE mode

Field 23 = Copy hierarchical DTE mode


The Spanpools report has two formats: user (-U option) and short (the default). Both formats list the server name and the pool data for each server. It lists the media IDs for each pool of media that share spanned backup images. When -mediaid appears on the command line, only the server pool and the disk pool that are related to that media ID appear.

If you want to process and use the output of bpimmedia, we recommend that you use the -l option. The output of bpimmedia that uses the -U or -L options may be truncated for the Backup-ID, Policy, and Host columns. The -U or -L options are useful when you want to obtain a quick, more readable view of the NetBackup images on media.

The user (-U) display format looks like the following:

# bpimmedia -spanpools -U
Related media pools containing spanned backup images, server plim:
  A00002  A00003

The short display format looks like the following

# bpimmedia -spanpools
POOL A00002 A00003
POOL 400032
Sun, 26 Jun 2022 12:00:00 -0500 en text/html https://www.veritas.com/support/en_US/doc/15263389-155723831-0/v14662479-155723831
Killexams : NetBackup™ Backup Planning and Performance Tuning Guide

You should have a well-documented and tested plan to recover from a logical error, an operator error, or a site disaster.

Information about disaster recovery is available in the following documents, which are found on the NetBackup Documentation Landing Page:

NetBackup Troubleshooting Guide (See Chapter 4: Disaster recovery)

NetBackup Administrator's Guide, Volumes I & II

NetBackup in Highly Available Environments Administrator's Guide

NetBackup Clustered Master Server Administrator's Guide

NetBackup Cloud Administrator's Guide

For recovery planning, use the following preparatory measures:

  • Always use a scheduled catalog backup.

    Refer to Catalog Recovery from an Online Backup in the NetBackup Troubleshooting Guide.

  • Review the disaster recovery plan often.

    Review your site-specific recovery procedures and verify that they are accurate and up-to-date. Also, verify that the more complex systems, such as the NetBackup master and media servers, have procedures for rebuilding the computers with the latest software.

    Performance depends on a chain of I/O events. The speed is only as good as the weakest link in that chain. For data recovery, you must consider I/O performance on the source, locality of the data, rehydration performance, and network performance.

    A number of NetBackup features optimize recovery, such as Instant Access and Instant Rollback for VMware.

    For MSDP-C the best recovery guidance is to have a reasonable amount of free space on the storage to use as a recovery cache.

  • Perform test recoveries on a regular basis.

    Implement a plan to perform restores of various systems to alternate locations. This plan should include selecting random production backups and restoring the data to a non-production system. A checksum can then be performed on one or many of the restored files and compared to the actual production data. Be sure to include off-site storage as part of this testing. The end user or application administrator can also help determine the integrity of the restored data.

  • Use and protect the NetBackup catalog.

    Do the following:

    • Back up the NetBackup catalog.

      The catalog contains information vital for NetBackup recovery. Its loss can result in hours or days of recovery time using manual processes.

    • Back up the catalog after each backup.

      If a catalog backup is used, an incremental catalog backup can be done after each backup session. Busy backup environments should also use a scheduled catalog backup, because their backup sessions end infrequently.

      In the event of a catastrophic failure, the recovery of images is slow if some images are not available. If a manual backup occurs shortly before the master server or the drive that contains the backed-up files crashes, the manual backup must be imported to recover the most recent version of the files.

    • Regularly confirm the integrity of the NetBackup catalog.

      Walk through the process of recovering a catalog from the device that contains the catalog backup on a regular basis, such as quarterly or after major operational or personnel changes. This essential part of NetBackup administration can save hours in the event of a catastrophe.

Sun, 26 Jun 2022 12:00:00 -0500 en text/html https://www.veritas.com/support/en_US/doc/21414900-146141073-0/v19527036-146141073
Killexams : Oracle PL SQL Tutorial

What is PL/SQL?

PL/SQL stands for Procedural Language extension of SQL.

PL/SQL is a combination of SQL along with the procedural features of programming languages. It was developed by Oracle Corporation in the early 90’s to enhance the capabilities of SQL.

The PL/SQL Engine:

Oracle uses a PL/SQL engine to processes the PL/SQL statements. A PL/SQL code can be stored in the client system (client-side) or in the database (server-side).

This Oracle PL SQL tutorial teaches you the basics of programming in PL/SQL with appropriate examples. You can use this tutorial as your guide or reference while programming with PL SQL. I will be making this Oracle PL SQL programming tutorial as often as possible to share my knowledge in PL SQL and help you in learning PL SQL better.

Even though the programming concepts discussed in this tutorial is specific to Oracle PL SQL. The concepts like cursors, functions and stored procedures can be used in other database systems like Sybase , Microsoft SQL server etc, with some change in syntax. This tutorial will be growing regularly; let us know if any Topic related to PL SQL needs to be added or you can also share your knowledge on PL SQL with us. Lets share our knowledge about PL SQL with others.
A Simple PL/SQL Block:

Each PL/SQL program consists of SQL and PL/SQL statements which from a PL/SQL block.

A PL/SQL Block consists of three sections:

    The Declaration section (optional).
    The Execution section (mandatory).
    The Exception (or Error) Handling section (optional).

Declaration Section:
The Declaration section of a PL/SQL Block starts with the reserved keyword DECLARE. This section is optional and is used to declare any placeholders like variables, constants, records and cursors, which are used to manipulate data in the execution section. Placeholders may be any of Variables, Constants and Records, which stores data temporarily. Cursors are also declared in this section.

Execution Section:
The Execution section of a PL/SQL Block starts with the reserved keyword BEGIN and ends with END. This is a mandatory section and is the section where the program logic is written to perform any task. The programmatic constructs like loops, conditional statement and SQL statements form the part of execution section.

Exception Section:
The Exception section of a PL/SQL Block starts with the reserved keyword EXCEPTION. This section is optional. Any errors in the program can be handled in this section, so that the PL/SQL Blocks terminates gracefully. If the PL/SQL Block contains exceptions that cannot be handled, the Block terminates abruptly with errors.

Every statement in the above three sections must end with a semicolon ; . PL/SQL blocks can be nested within other PL/SQL blocks. Comments can be used to document code.

This is how a trial PL/SQL Block looks.

     Variable declaration
     Program Execution
     Exception handling

Advantages of PL/SQL

These are the advantages of PL/SQL.

    Block Structures: PL SQL consists of blocks of code, which can be nested within each other. Each block forms a unit of a task or a logical module. PL/SQL Blocks can be stored in the database and reused.

     Procedural Language Capability: PL SQL consists of procedural language constructs such as conditional statements (if else statements) and loops like (FOR loops).

     Better Performance: PL SQL engine processes multiple SQL statements simultaneously as a single block, thereby reducing network traffic.

    Error Handling: PL/SQL handles errors or exceptions effectively during the execution of a PL/SQL program. Once an exception is caught, specific actions can be taken depending upon the type of the exception or it can be displayed to the user with a message.

PL/SQL Variables

These are placeholders that store the values that can change through the PL/SQL Block.

The General Syntax to declare a variable is:

variable_name datatype [NOT NULL := value ];

    variable_name is the name of the variable.
    datatype is a valid PL/SQL datatype.
    NOT NULL is an optional specification on the variable.
    value or DEFAULT valueis also an optional specification, where you can initialize a variable.
    Each variable declaration is a separate statement and must be terminated by a semicolon.

For example, if you want to store the current salary of an employee, you can use a variable.


salary  number (6);

* “salary” is a variable of datatype number and of length 6.

When a variable is specified as NOT NULL, you must initialize the variable when it is declared.

For example: The below example declares two variables, one of which is a not null.


salary number(4);

dept varchar2(10) NOT NULL := “HR Dept”;

The value of a variable can change in the execution or exception section of the PL/SQL Block. We can assign values to variables in the two ways given below.

1) We can directly assign values to variables.
    The General Syntax is:         

  variable_name:=  value;

2) We can assign values to variables directly from the database columns by using a SELECT.. INTO statement. The General Syntax is:

SELECT column_name

INTO variable_name

FROM table_name

[WHERE condition];

Example: The below program will get the salary of an employee with id '1116' and display it on the screen.


 var_salary number(6);

 var_emp_id number(6) = 1116;


 SELECT salary

 INTO var_salary

 FROM employee

 WHERE emp_id = var_emp_id;


 dbms_output.put_line('The employee '

      || var_emp_id || ' has  salary  ' || var_salary);



NOTE: The backward slash '/' in the above program indicates to execute the above PL/SQL Block.

Scope of Variables

PL/SQL allows the nesting of Blocks within Blocks i.e, the Execution section of an outer block can contain inner blocks. Therefore, a variable which is accessible to an outer Block is also accessible to all nested inner Blocks. The variables declared in the inner blocks are not accessible to outer blocks. Based on their declaration we can classify variables into two types.

    Local variables - These are declared in a inner block and cannot be referenced by outside Blocks.
    Global variables - These are declared in a outer block and can be referenced by its itself and by its inner blocks.

For Example: In the below example we are creating two variables in the outer block and assigning thier product to the third variable created in the inner block. The variable 'var_mult' is declared in the inner block, so cannot be accessed in the outer block i.e. it cannot be accessed after line 11. The variables 'var_num1' and 'var_num2' can be accessed anywhere in the block.


2>  var_num1 number;

3>  var_num2 number;


5>  var_num1 := 100;

6>  var_num2 := 200;


8>   var_mult number;

9>   BEGIN

10>    var_mult := var_num1 * var_num2;

11>   END;

12> END;

13> /

PL/SQL Constants

As the name implies a constant is a value used in a PL/SQL Block that remains unchanged throughout the program. A constant is a user-defined literal value. You can declare a constant and use it instead of actual value.

For example: If you want to write a program which will increase the salary of the employees by 25%, you can declare a constant and use it throughout the program. Next time when you want to increase the salary again you can change the value of the constant which will be easier than changing the actual value throughout the program.
The General Syntax to declare a constant is:

constant_name CONSTANT datatype := VALUE;

    constant_name is the name of the constant i.e. similar to a variable name.
    The word CONSTANT is a reserved word and ensures that the value does not change.
    VALUE - It is a value which must be assigned to a constant when it is declared. You cannot assign a value later.

For example, to declare salary_increase, you can write code as follows:


salary_increase CONSTANT number (3) := 10;

You must assign a value to a constant at the time you declare it. If you do not assign a value to a constant while declaring it and try to assign a value in the execution section, you will get a error. If you execute the below Pl/SQL block you will get error.


 salary_increase CONSTANT number(3);


 salary_increase := 100;

 dbms_output.put_line (salary_increase);


PL/SQL Records

What are records?

Records are another type of datatypes which oracle allows to be defined as a placeholder. Records are composite datatypes, which means it is a combination of different scalar datatypes like char, varchar, number etc.  Each scalar data types in the record holds a value. A record can be visualized as a row of data. It can contain all the contents of a row.
Declaring a record:
To declare a record, you must first define a composite datatype; then declare a record for that type.

The General Syntax to define a composite datatype is:

TYPE record_type_name IS RECORD

(first_col_name column_datatype,

second_col_name column_datatype, ...);

    record_type_name – it is the name of the composite type you want to define.
    first_col_name, second_col_name, etc.,- it is the names the fields/columns within the record.
    column_datatype defines the scalar datatype of the fields.

There are different ways you can declare the datatype of the fields.

1) You can declare the field in the same way as you declare the fieds while creating the table.
2) If a field is based on a column from database table, you can define the field_type as follows:

col_name table_name.column_name%type;

By declaring the field datatype in the above method, the datatype of the column is dynamically applied to the field.  This method is useful when you are altering the column specification of the table, because you do not need to change the code again.
NOTE: You can use also %type to declare variables and constants.

The General Syntax to declare a record of a uer-defined datatype is:

record_name record_type_name;

The following code shows how to declare a record called employee_rec based on a user-defined type.


TYPE employee_type IS RECORD

(employee_id number(5),

 employee_first_name varchar2(25),

 employee_last_name employee.last_name%type,

 employee_dept employee.dept%type);

 employee_salary employee.salary%type;

 employee_rec employee_type;

If all the fields of a record are based on the columns of a table, we can declare the record as follows:

record_name table_name%ROWTYPE;

For example, the above declaration of employee_rec can as follows:


 employee_rec employee%ROWTYPE;

The advantages of declaring the record as a ROWTYPE are:
1)  You do not need to explicitly declare variables for all the columns in a table.
2) If you alter the column specification in the database table, you do not need to update the code.

The disadvantage of declaring the record as a ROWTYPE is:
1) When u create a record as a ROWTYPE, fields will be created for all the columns in the table and memory will be used to create the datatype for all the fields. So use ROWTYPE only when you are using all the columns of the table in the program.

Conditional Statements in PL/SQL

As the name implies, PL/SQL supports programming language features like conditional statements, iterative statements.

The programming constructs are similar to how you use in programming languages like Java and C++. In this section I will provide you syntax of how to use conditional statements in PL/SQL programming.



IF condition


 statement 1;


 statement 2;



IF condition 1


 statement 1;

 statement 2;

ELSIF condtion2 THEN

 statement 3;


 statement 4;



IF condition 1


 statement 1;

 statement 2;

ELSIF condtion2 THEN

 statement 3;


 statement 4;



IF condition1 THEN


 IF condition2 THEN



ELSIF condition3 THEN



Iterative Statements in PL/SQL

An iterative control Statements are used when we want to repeat the execution of one or more statements for specified number of times. These are similar to those in

There are three types of loops in PL/SQL:
• Simple Loop
• While Loop
• For Loop
1) Simple Loop

A Simple Loop is used when a set of statements is to be executed at least once before the loop terminates. An EXIT condition must be specified in the loop, otherwise the loop will get into an infinite number of iterations. When the EXIT condition is satisfied the process exits from the loop.
The General Syntax to write a Simple Loop is:




   {or EXIT WHEN condition;}


These are the important steps to be followed while using Simple Loop.

1) Initialise a variable before the loop body.
2) Increment the variable in the loop.
3) Use a EXIT WHEN statement to exit from the Loop. If you use a EXIT statement without WHEN condition, the statements in the loop is executed only once.
2) While Loop

A WHILE LOOP is used when a set of statements has to be executed as long as a condition is true. The condition is evaluated at the beginning of each iteration. The iteration continues until the condition becomes false.
The General Syntax to write a WHILE LOOP is:

WHILE <condition>

 LOOP statements;


Important steps to follow when executing a while loop:

1) Initialise a variable before the loop body.
2) Increment the variable in the loop.
3) EXIT WHEN statement and EXIT statements can be used in while loops but it's not done oftenly.
3) FOR Loop

A FOR LOOP is used to execute a set of statements for a predetermined number of times. Iteration occurs between the start and end integer values given. The counter is always incremented by 1. The loop exits when the counter reachs the value of the end integer.

The General Syntax to write a FOR LOOP is:

FOR counter IN val1..val2

  LOOP statements;


    val1 - Start integer value.
    val2 - End integer value.

Important steps to follow when executing a while loop:

1) The counter variable is implicitly declared in the declaration section, so it's not necessary to declare it explicity.
2) The counter variable is incremented by 1 and does not need to be incremented explicitly.
3) EXIT WHEN statement and EXIT statements can be used in FOR loops but it's not done oftenly.

Thu, 25 Jan 2018 07:00:00 -0600 text/html https://www.siliconindia.com/online-courses/tutorials/Oracle-PL-SQL--Tutorial-id-13.html
Killexams : Services & Software No result found, try new keyword!A former network administrator for computer-monitor maker pleads guilty to illegally accessing a company server and deleting critical data two weeks after the firm had fired him. Big Blue hires a ... Wed, 29 Sep 2021 09:03:00 -0500 en text/html https://www.cnet.com/tech/services-and-software/2051/ Killexams : Neustar offers 10 percent off 10 or more short codes

Common short code registry Neustar Inc. is offering mobile application providers and aggregators 10 percent off purchases of 10 or more new codes through the end of the month.

There is no limit to the number of short code orders as long as a minimum of 10 codes are ordered before Aug. 31, although it does not apply to renewal orders. The customer's account will be credited no later than 30 days following the end of the program term.

"The strategy behind the promotion is trying to generate business from those customers -- application providers and aggregators -- that buy short codes on behalf of their customers as part of the mobile marketing ecosystem," said Matthew Valleskey, head of marketing for mobile services at Neustar, Sterling, VA.

"If you're Coke or Pepsi or another brand, in many cases you only need one short code, so this promotion is targeting vendors that buy codes in bulk," he said.

CTIA-The Wireless Association owns the Common Short Code Administration, and Neustar manages and operates the U.S. short codes registry on its behalf.

The CSCA's Web site lists top application providers and aggregators.

Tier-one aggregators include Air2Web, mBlox, Motricity, MX Telecom, OpenMarket, SinglePoint, Sybase 365, Upoc Networks, VeriSign and Vibes Media.

To get the word out about its promotion, Neustar sent out an email blast to selected vendors, application providers and aggregators who are current customers.

The promotion has prominent placement on the Neustar Web site. In addition, when members log into their account at the CSCA Web site, they are made aware of the promotion.

SMS marketing using a keyword-short-code call-to-action continues to grow, according to Neustar.

"Mobile marketing in general is growing -- more and more brands are looking to add mobile to their traditional marketing, and it's becoming more and more prevalent," Mr. Valleskey said. "SMS marketing is the most mature medium as far as mobile-based marketing is concerned, because its available on almost every handset out there, it doesn't require consumers to download any type of specific software and they don't have to have an Internet connection.

"Anyone can take advantage of an SMS marketing program -- SMS has the highest potential reach of any mobile marketing mediums out there," he said. "SMS has a potential reach of 270 million subscribers in the U.S., which is larger than any traditional channel out there."

Despite many successes, obstacles remain to widespread adoption of short-code-based marketing, above all time to market.

"There are obstacles to implementing an SMS program, because it's a little bit more complicated than traditional media," Mr. Valleskey said. "The ecosystem consists of app providers, aggregators that have to route traffic and get the campaign up and running on carriers' networks and the carriers themselves, so there are a few more hoops you have to jump through to get a campaign up and running.

"The time to market can be anywhere from two to eight to 12 weeks to get an SMS campaign up and running due to the provisioning time required by carriers," he said. "Neustar helps expedite that process."

Fri, 18 Dec 2020 05:09:00 -0600 en-US text/html https://www.marketingdive.com/ex/mobilemarketer/cms/news/messaging/3896.html
510-701 exam dump and training guide direct download
Training Exams List